Website review, no card needed
shawcontract.com website review
Visit site (opens in a new tab)Reviewed 29 October 202651 issues · 97 checks
This review found 51 issues worth fixing on shawcontract.com, 23 of them high impact, across 97 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.5 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 4.2 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 129 ms |
| May 16, 2026 | 130 ms |
| May 23, 2026 | 133 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 123 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 126 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 124 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 126 ms |
| Sep 19, 2026 | 124 ms |
| Sep 26, 2026 | 122 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 123 ms |
| Oct 24, 2026 | 129 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.9 s
1.8 s
2.7 s
3.5 s
4.4 s
5.3 s
6.2 s
7.1 s
Speed
Use efficient cache lifetimes
9.4 s · 4.3 MB35 files are served with short cache lifetimes, so returning visitors download them again (4.3 MB).
Improve image delivery
8.2 s · 2.3 MB9 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.2 s faster on a phone.
Reduce unused JavaScript
3.0 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
4.2 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, pure.cloud and Google Tag Manager and others), adding 3.2 MB and 3.2 s of main-thread time.
audioeye.com adds 940 ms
940 msaudioeye.com costs a phone 940 ms of main-thread work and 297 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.
pure.cloud adds 821 ms
821 mspure.cloud costs a phone 821 ms of main-thread work and 1.1 MB 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.
Reduce unused CSS
620 ms · 300 KiBAbout 300 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 620 ms faster on a phone.
Google Tag Manager adds 506 ms
506 msGoogle Tag Manager costs a phone 506 ms of main-thread work and 529 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.
Google CDN adds 468 ms
468 msGoogle CDN costs a phone 468 ms of main-thread work and 741 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.
Legacy JavaScript
450 ms · 81 KiBPolyfills for old browsers add 81 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 213 ms. During a long task the page ignores taps.
Minify JavaScript
110 KiB110 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 36 ms
36 msYour server sent the HTML in 36 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 17.2 s
17.2 sYour largest element takes 17.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 31.5 s
31.5 sThe page becomes fully interactive after 31.5 s. Good is under 3.8 s.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 750 ms
750 msScripts block taps and scrolling for 750 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 129 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.079
0.079The layout barely moves while loading (CLS 0.079, good is under 0.1).
Images and page weight
Page weight: 9.6 MB in 165 requests
9.6 MBYour homepage downloads 9.6 MB in 165 requests on a phone: images 5.2 MB (27), scripts 3.4 MB (57) and other files 526 KiB (48). Under 2 MB keeps phones on slow connections fast.
13 images far larger than shown
2.4 MB13 images are downloaded at several times the size a phone draws them, for example 5T758_57485_OVERHEAD2.webp at 2,048 px wide, shown at 390 px. Resized copies would save about 2.4 MB.
3 images over 500 KB
3 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.
11 images below the first screen load straight away
11 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (95 KiB) is 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.
About 2.7 g of CO₂ per visit
2.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.72 g of CO₂e: 327.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Commercial Carpet Tile, Broadloom Carpet, LVT Flooring | ShawContract”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
185 internal links, 12 external
The homepage links to 185 pages on shawcontract.com and 12 external pages.
4 checks passed
Meta description: 115 characters
Your meta description is 115 characters: “Easily search and find the best Commercial LVT, Modular Carpet, Tile, Porcelain & More. View & Order Samples Today!”.
Canonical URL set
The canonical URL is https://www.shawcontract.com/en-us.
Structured data in place
Structured data found: Organization.
XML sitemap found
Your XML sitemap is reachable at https://www.shawcontract.com/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
3 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (980 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.shawcontract.com/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.shawcontract.com/en-us and https://www.shawcontract.com/en-us/home all use the title “Commercial Carpet Tile, Broadloom Carpet, LVT Flooring | ShawContract”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://www.shawcontract.com/en-us/resources, https://www.shawcontract.com/en-us/contactus, https://www.shawcontract.com/en-us/media-room, https://www.shawcontract.com/en-us/design/selectliving, https://www.shawcontract.com/en-us/design/selectoffice and https://www.shawcontract.com/en-us/design/selectone and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.shawcontract.com/en-us/home, whose canonical is https://www.shawcontract.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 pages without an H1
https://www.shawcontract.com/en-us/about/about-us, https://www.shawcontract.com/en-us/resources, https://www.shawcontract.com/en-us/media-room, https://www.shawcontract.com/en-us/showrooms, https://www.shawcontract.com/en-us/home and https://www.shawcontract.com/en-us/design/selectliving and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.shawcontract.com/en-us/contactus, https://www.shawcontract.com/en-us/showrooms and https://www.shawcontract.com/en-us/design/selecttwo-broadloom have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
5 pages slow to respond
https://www.shawcontract.com/en-us/contactus, https://www.shawcontract.com/en-us/media-room, https://www.shawcontract.com/en-us/design/selectliving, https://www.shawcontract.com/en-us/design/selectoffice and https://www.shawcontract.com/en-us/design/selectedu took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 128 found) and read each the way a search engine does.
3 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 637 words of copy
The homepage carries about 637 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Sign Up” and “Order History”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
23 cookies set on arrival
23Opening the homepage sets 23 cookies (measured from a US location before any click).
28 other companies contacted
Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at shawcontract.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on shawcontract.com, including 23 speed issues, 5 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.