WillSeal (willseal.com) – Full Analysis



(Took us an average of 1.4 seconds to load)

Table of Contents
Basic 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 willseal.com

Email: custserv (at) willseal (dot) com

Social media profiles:

    Using HTTPS: Yes 🙂

    HTML errors found on homepage

    1600px" /><h2 style="box-shadow: 0px 4px 10px -5px black; text-shadow: none; font-weight: normal; opacity: .65; width:600px; text-align:left;padding-top:15px;padding-bottom:15px;padding-left:30px;font-size:25px;color:#ffffff;width:982px;top:300px;left:70px;background-color:black;line-height:falsepx;white-space:normal;" class="ls-l" data-ls="durationin:900;delayin:1400;fadein:false;durationout:900;fadeout:false;slidedirection:bottom;slideoutdirection:bottom;delayout:200;">Choose
    CSS: “line-height”: “falsepx” is not a “line-height” value.

    marks</h2><h2 style="box-shadow: 0px 0px 0px 0px black; text-shadow: none; font-weight: normal; opacity: .65; width:390px; text-align:left;padding-top:10px;padding-bottom:10px;padding-left:20px;font-size:16px;color:#ffffff;width:355px;top:380px;left:70px;background-color:black;line-height:falsepx;white-space:normal;" class="ls-l" data-ls="durationin:900;delayin:1400;fadein:false;durationout:900;fadeout:false;slidedirection:bottom;slideoutdirection:bottom;delayout:200;">Empire
    CSS: “line-height”: “falsepx” is not a “line-height” value.

    text" ><p><center></cent
    The “center” element is obsolete. Use CSS instead.

    ></center></p><h4 s
    No “p” element in scope but a “p” end tag seen.

    ppear --><img style="width: 100%; margin: auto; display: block;" class="vidyard-player-embed" src="https://play.vidyard.com/FVcjSQDqSiUsY9S7Gi1Apo.jpg" data-uuid="FVcjSQDqSiUsY9S7Gi1Apo" data-v="4" data-type="inline"/></div>
    An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

    y: none;"></p><ul>
    No “p” element in scope but a “p” end tag seen.

    y: none;"></p><h5>S
    No “p” element in scope but a “p” end tag seen.

    Popular words

    Word Frequency
    willseal 19
    products 10
    joint 7
    expansion 7
    building 6
    design 6
    fire 6
    read 5
    moisture 5
    safety 5
    commercial 4
    sealants 4
    astm 4
    foam 4
    dynamic 4
    joints 4
    stadium 4
    privacy 4
    waterproofing 3
    solutions 3

    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

    Minify JavaScript: Minifying JavaScript files can reduce payload sizes and script parse time.
    Potential savings of 140 KiB

    Properly size images: Serve images that are appropriately-sized to save cellular data and improve load time.
    Potential savings of 216 KiB

    Reduce unused JavaScript: Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
    Potential savings of 505 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.
    Potential savings of 770 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 1 KiB

    Efficiently encode images: Optimized images load faster and consume less cellular data.
    Potential savings of 519 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.
    Potential savings of 1,340 KiB

    Reduce unused CSS: Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
    Potential savings of 728 KiB

    Minify CSS: Minifying CSS files can reduce network payload sizes.
    Potential savings of 77 KiB

    Enable text compression: Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
    Potential savings of 1,446 KiB

    Internal pages [TOP 20]

    Website Page
    https://willseal.com/[email protected]

    External homepage links [TOP 20]

    Website Page