Website review, no card needed
crownworkspace.com website review
Visit site (opens in a new tab)Reviewed 20 October 202631 issues · 76 checks
This review found 31 issues worth fixing on crownworkspace.com, 11 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.8 s |
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.5 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 155 ms |
| May 9, 2026 | 156 ms |
| May 16, 2026 | 154 ms |
| May 23, 2026 | 151 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 142 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 142 ms |
| Jul 4, 2026 | 142 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 143 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 141 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 151 ms |
| Oct 10, 2026 | 148 ms |
| Oct 17, 2026 | 149 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
Render-blocking requests
2.9 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Mobile performance score: 62
62/100Your mobile performance score is 62 (desktop: 94). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Optanon and Matomo and others), adding 1.0 MB and 625 ms of main-thread time.
Reduce unused JavaScript
150 ms · 444 KiBAbout 444 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 493 ms
493 msGoogle Tag Manager costs a phone 493 ms of main-thread work and 662 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.
Reduce unused CSS
300 ms · 78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Legacy JavaScript
200 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Improve image delivery
218 KiB9 images could be 218 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 172 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 19 KiB19 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
59 KiB7 files are served with short cache lifetimes, so returning visitors download them again (59 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 94 but mobile only 62. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 659 ms of it running JavaScript. That is comfortably low.
Server response: 25 ms
25 msYour server sent the HTML in 25 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: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
Real-user TTFB: 2.7 s
2.7 sReal visitors wait 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 12.6 s
12.6 sThe page becomes fully interactive after 12.6 s. Good is under 3.8 s.
Largest Contentful Paint: 5.8 s
5.8 sYour largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Tailored Approach to Commercial Moves and Interiors Excep…”.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 351 ms
351 msScripts block taps and scrolling for 351 ms in total while the page loads. Good is under 200 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 155 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 149 ms
149 msReal visitors wait 149 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.8 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 107 requests
2.8 MBYour homepage downloads 2.8 MB in 107 requests on a phone: images 1.2 MB (48), scripts 1,018 KiB (27) and fonts 480 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 95.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
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 47 images in the HTML carry an alt attribute.
9 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 12 WCAG 2.2 A/AA and best-practice rules on the phone render: 9 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
72 internal links, 17 external
The homepage links to 72 pages on crownworkspace.com and 17 external pages.
8 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “A tailored approach to office design, interior fit-outs and commercial relocations. From space planning to fit-outs, we…”.
One H1 headline
Your main headline reads: “A Tailored Approach to Commercial Moves and Interiors”.
Title: 52 characters
Your title is a healthy 52 characters: “Office Movers & Space Planning - Crown Workspace USA”.
Canonical URL set
The canonical URL is https://crownworkspace.com/us/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://crownworkspace.com/sitemap_index.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.
No llms.txt
There is no https://crownworkspace.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.
1 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.
Other pages
2 pages share a title
https://crownworkspace.com/us?noredirect=true and / all use the title “Office Movers & Space Planning - Crown Workspace USA”. 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://crownworkspace.com/us/case-studies has 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 /, whose canonical is https://crownworkspace.com/us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has an H1
Each page we checked has a main headline.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
1 checks passed
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 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 33 words
The homepage has only about 33 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.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”.
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks and 4 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
1 checks passed
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 crownworkspace.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on crownworkspace.com, including 16 speed issues, 2 SEO issues and 3 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.