Website review, no card needed
serviceworks.xyz website review
Visit site (opens in a new tab)Reviewed 5 November 202623 issues · 77 checks
This review found 23 issues worth fixing on serviceworks.xyz, 8 of them high impact, across 77 checks. The most urgent: improve image delivery. 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
87B- #7,749 of 111,105 reviewed websitesbeats 90%
- #4,549 of 63,365 online storesbeats 89%
- #4,416 of 57,856 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 941 ms |
| May 23, 2026 | 901 ms |
| May 30, 2026 | 858 ms |
| Jun 6, 2026 | 818 ms |
| Jun 13, 2026 | 809 ms |
| Jun 20, 2026 | 819 ms |
| Jun 27, 2026 | 837 ms |
| Jul 4, 2026 | 846 ms |
| Jul 11, 2026 | 860 ms |
| Jul 18, 2026 | 863 ms |
| Jul 25, 2026 | 841 ms |
| Aug 1, 2026 | 833 ms |
| Aug 8, 2026 | 845 ms |
| Aug 15, 2026 | 843 ms |
| Aug 22, 2026 | 855 ms |
| Aug 29, 2026 | 865 ms |
| Sep 5, 2026 | 859 ms |
| Sep 12, 2026 | 862 ms |
| Sep 19, 2026 | 845 ms |
| Sep 26, 2026 | 826 ms |
| Oct 3, 2026 | 808 ms |
| Oct 10, 2026 | 788 ms |
| Oct 17, 2026 | 785 ms |
| Oct 24, 2026 | 790 ms |
| Oct 31, 2026 | 798 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 89 ms |
| May 23, 2026 | 89 ms |
| May 30, 2026 | 90 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 90 ms |
| Jun 20, 2026 | 90 ms |
| Jun 27, 2026 | 91 ms |
| Jul 4, 2026 | 92 ms |
| Jul 11, 2026 | 93 ms |
| Jul 18, 2026 | 93 ms |
| Jul 25, 2026 | 92 ms |
| Aug 1, 2026 | 92 ms |
| Aug 8, 2026 | 93 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 93 ms |
| Sep 12, 2026 | 92 ms |
| Sep 19, 2026 | 90 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 88 ms |
| Oct 17, 2026 | 89 ms |
| Oct 24, 2026 | 89 ms |
| Oct 31, 2026 | 90 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.9 s
2.8 s
3.8 s
4.7 s
5.7 s
6.6 s
7.6 s
Speed
Improve image delivery
1.6 s · 1.2 MB16 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
3,143 HTML elements
The page has 3,143 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 735 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 83 ms
83 msShopify costs a phone 83 ms of main-thread work and 365 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.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and Google Tag Manager and others), adding 937 KiB and 331 ms of main-thread time.
Reduce unused JavaScript
150 ms · 229 KiBAbout 229 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.
Reduce unused CSS
150 ms · 42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
81 KiB12 files are served with short cache lifetimes, so returning visitors download them again (81 KiB).
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 76 ms. During a long task the page ignores taps.
Minify JavaScript
22 KiB22 KiB could be saved by minifying JavaScript.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
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: 46 ms
46 msYour server sent the HTML in 46 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.4 s
10.4 sYour largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 14.6 s
14.6 sThe page becomes fully interactive after 14.6 s. Good is under 3.8 s.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 89 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 103 ms
103 msReal visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 367 ms
367 msReal visitors wait 367 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 84 ms
84 msScripts block the page for only 84 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 4.8 MB in 262 requests
4.8 MBYour homepage downloads 4.8 MB in 262 requests on a phone: images 2.7 MB (27), scripts 946 KiB (107) and other files 786 KiB (91). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.35 g of CO₂e: 162.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (20 characters)
Your title is only 20 characters: “Service Works London”. 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.
84 internal links, 3 external
The homepage links to 84 pages on serviceworks.xyz and 3 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Service Works London”.
Canonical URL set
The canonical URL is https://serviceworks.xyz/.
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://serviceworks.xyz/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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (957 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://serviceworks.xyz/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
10 pages without a meta description
https://serviceworks.xyz/collections/womens, https://serviceworks.xyz/collections/shirts, https://serviceworks.xyz/collections/hoodies, https://serviceworks.xyz/collections/knitwear, https://serviceworks.xyz/collections/hats and https://serviceworks.xyz/collections/accessories and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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 15 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: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
12 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 557 words of copy
The homepage carries about 557 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
4 calls to action
The homepage has 4 calls to action, for example “Shop icon-chevron Expand submenu”, “Shop” and “Shop now”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
19 cookies set on arrival
19Opening the homepage sets 19 cookies (measured from a US location before any click).
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.
42 other companies contacted
Loading the homepage contacts 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 serviceworks.xyz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Gorgias Live Chat Helpdesk · Simprosys Google Shopping Feed · Swap Shipping Returns · Klaviyo Email Marketing Sms · Judge Me Reviews · Gdpr Backpack · Oron Test App · useamp.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on serviceworks.xyz, including 9 speed issues, 3 SEO issues and 1 conversion gap. 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.