- HOAST (hoast.org) – Full Analysis - March 1, 2021
- SallyMillerYoga (sallymilleryoga.com) – Full Analysis - March 1, 2021
- bentandbree.com – Full Analysis - March 1, 2021
(Took us an average of 0.6 seconds to load)
|Table of Contents|
|Minor HTML issues found on homepage|
|How can this website be improved?|
|Websites linked to|
Basic information for trenchdrainmaterials.com
About: We are your go to for trench drain products. The best products at the lowest prices NDS, JOSAM, ACO, Neenah and many more. Fast and Free nationwide shipping
Email or contact page: [email protected]
Social media profiles:
Using HTTPS: Yes 🙂
|Nameservers||[‘BONNIE.NS.CLOUDFLARE.COM’, ‘HUGH.NS.CLOUDFLARE.COM’, ‘hugh.ns.cloudflare.com’, ‘bonnie.ns.cloudflare.com’]|
|Status||[‘clientTransferProhibited https://icann.org/epp#clientTransferProhibited’, ‘clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited’]|
|[‘[email protected]’, ‘[email protected]’, ‘[email protected]’]|
|Name||Contact Privacy Inc. Customer 0147764741|
|Organization||Contact Privacy Inc. Customer 0147764741|
|Address||96 Mowat Ave|
HTML errors found on homepage
="UTF-8"><meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"><meta
A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.
CSS: “etter-spacing”: Property “etter-spacing” doesn’t exist.
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-KWKTNT2"height="0" width="0" style="display:none;visibility:hidden"></ifra
Bad start tag in “iframe” in “noscript” in “head”.
Stray end tag “noscript”.
Stray end tag “head”.
</head><body data-rsssl=1 class="home page-template-default page page-id-1001252 theme-yellowbusiness woocommerce-no-js"><div
Start tag “body” seen but an element of the same type was already open.
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: FAST. 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: FAST. Measures how long the main part of the website takes to load.
Opportunities for improvement
Potential savings of 118 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 178 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 440 ms
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 117 KiB
Avoid multiple page redirects: Redirects introduce additional delays before the page can be loaded. [Learn more](https://web.dev/redirects/).
Potential savings of 3,380 ms
Efficiently encode images: Optimized images load faster and consume less cellular data. [Learn more](https://web.dev/uses-optimized-images/).
Potential savings of 69 KiB
Properly size images: Serve images that are appropriately-sized to save cellular data and improve load time. [Learn more](https://web.dev/uses-responsive-images/).
Potential savings of 79 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 870 ms