Daorong (daorong.us) – Full Analysis


道融 Daorong – Built with SitePad

(Took us an average of 2.1 seconds to load)

Table of Contents
Basic information
Whois information
Minor HTML issues found on homepage
Popular words
Pagespeed analysis
How can this website be improved?
Internal pages
Websites linked to

Basic information for daorong.us

Email or contact page: http://daorong.us/contact/

Social media profiles:

    Using HTTPS: Yes 🙂

    Whois information

    HTML errors found on homepage

    cript><title>道融 Daorong &
    Forbidden code point U+0081.

    t><title>道融 Daorong &#821
    Forbidden code point U+008d.

    s+xml" title="道融 Daorong &
    Forbidden code point U+0081.

    l" title="道融 Daorong &raqu
    Forbidden code point U+008d.

    r-header"><div pagelayer-id="5dbyaph7q0jp1dqf" class="pagelayer-row pagelayer-row-stretch-auto pagelayer-height-default">
    Attribute “pagelayer-id” not allowed on element “div” at this point.

    "> <style pagelayer-style-id="5dbyaph7q0jp1dqf">[pagel
    Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)

    -content: default}[pag
    CSS: “align-content”: “default” is not a “align-content” value.

    th-auto"><div pagelayer-id="p5m1v3vo0oa8l85s" class="pagelayer-col pagelayer-col-4">
    Attribute “pagelayer-id” not allowed on element “div” at this point.

    "> <style pagelayer-style-id="p5m1v3vo0oa8l85s">[pagel
    Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)

    -holder"><div pagelayer-id="yEI8nkgeLRZ7jyRg" class="pagelayer-wp_title">
    Attribute “pagelayer-id” not allowed on element “div” at this point.

    Popular words

    Word Frequency
    daorong 3
    home 1
    contact 1
    mission 1
    success 1
    highly 1
    professional 1
    law 1
    firm 1
    loyal 1
    efficient 1
    welcome 1
    office 1
    sign 1
    get 1
    preliminary 1
    book 1
    appointment 1

    Pagespeed analysis

    OVERALL SITE SPEED: AVERAGE (details below)

    CUMULATIVE LAYOUT SHIFT SCORE: AVERAGE. Have you ever been reading an article online when something suddenly changes on the page? Without warning, the text moves, and you’ve lost your place. Or even worse: you’re about to tap a link or a button, but in the instant before your finger lands—BOOM—the link moves, and you end up clicking something else! This is a measure of how often this is happening on your website.

    FIRST CONTENTFUL PAINT MS SCORE: AVERAGE. This measures the time taken for the first thing on your website to load when a visitor goes there.

    FIRST INPUT DELAY MS SCORE: AVERAGE. How long it takes for your website to react if the user interacts with it in some way, such as clicking a link or button.

    LARGEST CONTENTFUL PAINT MS SCORE: AVERAGE. Measures how long the main part of the website takes to load.

    Opportunities for improvement

    Enable text compression: Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more](https://web.dev/uses-text-compression/).
    Potential savings of 56 KiB

    Serve images in next-gen formats: Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more](https://web.dev/uses-webp-images/).
    Potential savings of 800 KiB

    Eliminate render-blocking resources: Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn more](https://web.dev/render-blocking-resources/).
    Potential savings of 700 ms

    Avoid serving legacy JavaScript to modern browsers: Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren’t necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. [Learn More](https://philipwalton.com/articles/deploying-es2015-code-in-production-today/)
    Potential savings of 0 KiB

    Remove unused JavaScript: Remove unused JavaScript to reduce bytes consumed by network activity. [Learn more](https://web.dev/unused-javascript/).
    Potential savings of 72 KiB

    Remove unused CSS: Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. [Learn more](https://web.dev/unused-css-rules/).
    Potential savings of 67 KiB

    Minify CSS: Minifying CSS files can reduce network payload sizes. [Learn more](https://web.dev/unminified-css/).
    Potential savings of 7 KiB

    Preload key requests: Consider using `` to prioritize fetching resources that are currently requested later in page load. [Learn more](https://web.dev/uses-rel-preload/).
    Potential savings of 280 ms

    Efficiently encode images: Optimized images load faster and consume less cellular data. [Learn more](https://web.dev/uses-optimized-images/).
    Potential savings of 117 KiB

    Internal pages [TOP 20]

    Website Page

    External homepage links [TOP 20]

    Website Page