Website review, no card needed
thewhitecompany.com website review
Visit site (opens in a new tab)Reviewed 2 November 202636 issues · 70 checks
This review found 36 issues worth fixing on thewhitecompany.com, 12 of them high impact, across 70 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 11.5 s |
| May 23, 2026 | 14.3 s |
| May 30, 2026 | 17.0 s |
| Jun 6, 2026 | 18.5 s |
| Jun 13, 2026 | 17.6 s |
| Jun 20, 2026 | 14.1 s |
| Jun 27, 2026 | 10.4 s |
| Jul 4, 2026 | 8.0 s |
| Jul 11, 2026 | 8.2 s |
| Jul 18, 2026 | 8.0 s |
| Jul 25, 2026 | 8.1 s |
| Aug 1, 2026 | 7.5 s |
| Aug 8, 2026 | 6.4 s |
| Aug 15, 2026 | 6.5 s |
| Aug 22, 2026 | 6.4 s |
| Aug 29, 2026 | 6.6 s |
| Sep 5, 2026 | 6.9 s |
| Sep 12, 2026 | 7.6 s |
| Sep 19, 2026 | 7.9 s |
| Sep 26, 2026 | 8.0 s |
| Oct 3, 2026 | 7.7 s |
| Oct 10, 2026 | 7.4 s |
| Oct 17, 2026 | 7.0 s |
| Oct 24, 2026 | 6.4 s |
| Oct 31, 2026 | 6.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 397 ms |
| May 23, 2026 | 479 ms |
| May 30, 2026 | 547 ms |
| Jun 6, 2026 | 568 ms |
| Jun 13, 2026 | 519 ms |
| Jun 20, 2026 | 408 ms |
| Jun 27, 2026 | 329 ms |
| Jul 4, 2026 | 296 ms |
| Jul 11, 2026 | 306 ms |
| Jul 18, 2026 | 310 ms |
| Jul 25, 2026 | 308 ms |
| Aug 1, 2026 | 297 ms |
| Aug 8, 2026 | 278 ms |
| Aug 15, 2026 | 272 ms |
| Aug 22, 2026 | 269 ms |
| Aug 29, 2026 | 269 ms |
| Sep 5, 2026 | 277 ms |
| Sep 12, 2026 | 304 ms |
| Sep 19, 2026 | 339 ms |
| Sep 26, 2026 | 370 ms |
| Oct 3, 2026 | 397 ms |
| Oct 10, 2026 | 405 ms |
| Oct 17, 2026 | 395 ms |
| Oct 24, 2026 | 381 ms |
| Oct 31, 2026 | 365 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
1.9 s · 292 KiB12 files are served with short cache lifetimes, so returning visitors download them again (292 KiB).
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused JavaScript
450 ms · 90 KiBAbout 90 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 431 ms. During a long task the page ignores taps.
3 third-party services on the page
3 third-party services load with your homepage (mPulse, Adobe TypeKit and Optanon), adding 189 KiB and 20 ms of main-thread time.
Improve image delivery
28 KiB2 images could be 28 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 1.3 s of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 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 LCP: 6.1 s
6.1 sReal visitors wait 6.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.32
0.32For real visitors the layout shifts by 0.32 (75th percentile). Good is under 0.1.
Real-user FCP: 3.8 s
3.8 sReal visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a bedroom with a bed, fireplace, and a chair in it”.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user INP: 365 ms
365 msReal visitors wait 365 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.163
0.163The layout shifts by 0.163 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 5.0 s
5.0 sThe page becomes fully interactive after 5.0 s. Good is under 3.8 s.
Total Blocking Time: 278 ms
278 msScripts block taps and scrolling for 278 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
3 checks passed
Real-user TTFB: 769 ms
769 msReal visitors wait 769 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 397 ms to 365 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 51% faster for real visitors
-51%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 11.5 s to 6.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
An image on the first screen is lazy-loaded
TT_5star_bedroom_Feature_Hero_Img_8 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.2 g of CO₂ per visit
0.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.16 g of CO₂e: 19.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 592 KiB in 20 requests
592 KiBYour homepage downloads 592 KiB in 20 requests on a phone: scripts 404 KiB (8), fonts 132 KiB (3) and images 42 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 checks passed
Every image has alt text
All 2 images in the HTML carry an alt attribute.
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 0 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex,follow”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (22 characters)
Your title is only 22 characters: “The White Company - US”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 3 internal links
The homepage links to only 3 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
3 checks passed
One H1 headline
Your main headline reads: “We're sorry. The White Company is not currently able to ship orders to the United States of America”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.thewhitecompany.com/uk/uk-sitemap.xml.
AI search readiness
No Organization structured data
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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
llms.txt published
The site publishes https://www.thewhitecompany.com/llms.txt (19 KiB, 186 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.thewhitecompany.com/uk is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.thewhitecompany.com/us?countryIsoCode=US¤cyIsoCode=USD&clear=true and https://www.thewhitecompany.com/uk all use the title “The White Company - US”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.thewhitecompany.com/uk has no meta description, so Google writes the search snippet from whatever text it finds.
1 internal page checked
We fetched 1 page linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 1 page we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 55 words
The homepage has only about 55 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 thewhitecompany.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
- Akamai
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on thewhitecompany.com, including 16 speed issues, 8 SEO issues and 6 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.