quikrete.com website review

About 4.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 26.4 s faster on a phone.

14 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

YouTube costs a phone 2.7 s of main-thread work and 7.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 180 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.

Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 7.9 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (YouTube, Google Tag Manager and weglot.com and others), adding 9.3 MB and 3.4 s of main-thread time.

22 files are served with short cache lifetimes, so returning visitors download them again (378 KiB).

19 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

Google Tag Manager costs a phone 388 ms of main-thread work and 623 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

20 long tasks block the main thread while loading, the longest for 257 ms. During a long task the page ignores taps.

LiveChat costs a phone 51 ms of main-thread work and 417 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The first text or image appears after 35.3 s on a phone. Good is under 1.8 s.

Your largest element takes 53.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Renew Old, Worn Concrete SurfacesWalk On in 8 Hours and Dri…”.

Visually, the page fills in at 35.3 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 73.7 s. Good is under 3.8 s.

Scripts block taps and scrolling for 673 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.

25 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 116 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.3 MB in 300 requests on a phone: scripts 8.9 MB (97), images 4.5 MB (87) and other files 1.4 MB (57). Under 2 MB keeps phones on slow connections fast.

featured-5-products.png weighs 692 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example featured-5-products.png at 1,000 px wide, shown at 120 px. Resized copies would save about 731 KiB.

25 images (3.8 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

3 images further down the page (515 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 4.62 g of CO₂e: 554.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 frame has no title, so screen-reader users cannot tell what it contains.

1 image has no alt text, which hurts accessibility and image search.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 82 characters, so Google will cut it off around 60: “Largest Manufacturer of Packaged Concrete | QUIKRETE: Cement and Concrete Products”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 89 pages on quikrete.com and 26 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.quikrete.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.quikrete.com/productlines/cements/portland-cement.asp, https://www.quikrete.com/productlines/cements/slag-cement.asp, https://www.quikrete.com/productlines/cements/packaged-cements.asp and https://www.quikrete.com/productlines/cements/ready-mix-cement.asp declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://www.quikrete.com/construction-products-guide has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.quikrete.com/productlines/cements/portland-cement.asp, https://www.quikrete.com/productlines/cements/slag-cement.asp, https://www.quikrete.com/productlines/cements/packaged-cements.asp and https://www.quikrete.com/productlines/cements/ready-mix-cement.asp use the same meta description. A description written for each page earns more clicks.

https://www.quikrete.com/productlines/cements/portland-cement.asp, https://www.quikrete.com/productlines/cements/slag-cement.asp, https://www.quikrete.com/productlines/cements/packaged-cements.asp, https://www.quikrete.com/productlines/cements/ready-mix-cement.asp, https://www.quikrete.com/construction-products-guide and https://www.quikrete.com/dealers and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 456 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 7 cookies, 5 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.