Website review, no card needed
dalstrong.co.uk website review
Visit site (opens in a new tab)Reviewed 7 November 202635 issues · 85 checks
This review found 35 issues worth fixing on dalstrong.co.uk, 11 of them high impact, across 85 checks. The most urgent: fails Core Web Vitals for real visitors. 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
77C- #68,795 of 123,879 reviewed websitesbeats 39%
- #44,530 of 69,698 online storesbeats 31%
- #42,350 of 63,406 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 130 ms |
| May 23, 2026 | 133 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 133 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 123 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 132 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 143 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 136 ms |
| Aug 8, 2026 | 132 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 134 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 139 ms |
| Oct 3, 2026 | 136 ms |
| Oct 10, 2026 | 133 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 147 ms |
| Oct 31, 2026 | 147 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.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.5 s
5.2 s
5.9 s
Speed
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Clarity and others), adding 1.5 MB and 1.2 s of main-thread time.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 873 ms
873 msGoogle Tag Manager costs a phone 873 ms of main-thread work and 966 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 JavaScript
150 ms · 768 KiBAbout 768 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.
Render-blocking requests
650 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,420 HTML elements
The page has 2,420 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 147 ms
147 msKlaviyo costs a phone 147 ms of main-thread work and 307 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
150 ms · 96 KiBAbout 96 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 209 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
159 KiB13 files are served with short cache lifetimes, so returning visitors download them again (159 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Improve image delivery
6 KiB1 image could be 6 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.
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: 9 ms
9 msYour server sent the HTML in 9 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 CLS: 0.36
0.36For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.
Time to Interactive: 17.0 s
17.0 sThe page becomes fully interactive after 17.0 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 691 ms
691 msScripts block taps and scrolling for 691 ms in total while the page loads. Good is under 200 ms.
63 images without width and height
63 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 3.7 s
3.7 sYour largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dalstrong UK”.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 147 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 150 ms
150 msReal visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 436 ms
436 msReal visitors wait 436 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
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.
Images and page weight
Page weight: 2.9 MB in 229 requests
2.9 MBYour homepage downloads 2.9 MB in 229 requests on a phone: scripts 1.8 MB (80), other files 783 KiB (121) and images 234 KiB (17). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (61 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 100.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Certain ARIA roles must be contained by particular parents (1 element)
Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
67 links without text
67 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 2 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 (12 characters)
Your title is only 12 characters: “Dalstrong UK”. 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 social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
303 internal links, 16 external
The homepage links to 303 pages on dalstrong.co.uk and 16 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Dalstrong UK”.
Canonical URL set
The canonical URL is https://www.dalstrong.co.uk/.
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.dalstrong.co.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.
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 (1,322 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.dalstrong.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without a meta description
https://www.dalstrong.co.uk/pages/compare, https://www.dalstrong.co.uk/collections/essential-knives, https://www.dalstrong.co.uk/collections/chefs-knife, https://www.dalstrong.co.uk/collections/paring-knife, https://www.dalstrong.co.uk/collections/butcher-knife and https://www.dalstrong.co.uk/collections/cleaver-knife and 5 others 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.dalstrong.co.uk/collections/specialty-knives-1, whose canonical is https://www.dalstrong.co.uk/collections/specialty-knives. 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 113 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 broken image
1 image failed to load on a phone, for example https://www.dalstrong.co.uk/.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://ipinfo.io/json' from origin 'https://www.dalstrong.co.uk' has been blocked by CORS policy: …”.
2 checks passed
Tap targets are thumb-sized
60 of 62 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 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 376 words of copy
The homepage carries about 376 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: “SHOP CHEF'S KNIVES”.
18 calls to action
The homepage has 18 calls to action, for example “SHOP ESSENTIAL KNIVES”, “SHOP SPECIALTY KNIVES” and “SHOP BY SERIES”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
37 other companies contacted
Loading the homepage contacts 37 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 dalstrong.co.uk, 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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · b-cdn.net · printful.com · nice-team.net · goaffpro.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
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- smartrecruiters
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on dalstrong.co.uk, including 15 speed issues, 4 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.