Website review, no card needed
dezines.co.uk website review
Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 84 checks
This review found 33 issues worth fixing on dezines.co.uk, 8 of them high impact, across 84 checks. The most urgent: page weight: 4.0 MB in 128 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
75CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.5 s
3.3 s
4.1 s
4.9 s
5.7 s
6.6 s
Speed
Reduce unused JavaScript
610 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and cdn-website.com and others), adding 3.8 MB and 1.2 s of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
550 ms · 263 KiB20 files are served with short cache lifetimes, so returning visitors download them again (263 KiB).
Reduce unused CSS
460 ms · 106 KiBAbout 106 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.
cloudfront.net adds 346 ms
346 mscloudfront.net costs a phone 346 ms of main-thread work and 847 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.
cdn-website.com adds 254 ms
254 mscdn-website.com costs a phone 254 ms of main-thread work and 1.4 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.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 295 ms
295 msGoogle Tag Manager costs a phone 295 ms of main-thread work and 437 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.
paperform.co adds 138 ms
138 mspaperform.co costs a phone 138 ms of main-thread work and 367 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.
1,627 HTML elements
The page has 1,627 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
multiscreensite.com adds 93 ms
93 msmultiscreensite.com costs a phone 93 ms of main-thread work and 531 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.
Improve image delivery
150 ms · 99 KiB6 images could be 99 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
33 KiBPolyfills for old browsers add 33 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: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.6 s
21.6 sThe page becomes fully interactive after 21.6 s. Good is under 3.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A group of people are sitting around a table looking at a c…”.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.276
0.276The layout shifts by 0.276 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 246 ms
246 msScripts block taps and scrolling for 246 ms in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
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: 4.0 MB in 128 requests
4.0 MBYour homepage downloads 4.0 MB in 128 requests on a phone: scripts 2.2 MB (40), images 1.3 MB (42) and fonts 214 KiB (11). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 137.1 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
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail 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 (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 48 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (258 characters)
Your title is 258 characters, so Google will cut it off around 60: “DEZINES | PaaS SaaS ECOMMERCE | Responsive Website Builder | Pre-built DIY Websites | £35…”.
5 H1 headlines
There are 5 <h1> headlines (“DEZINES is a Strategic Commercial Consultancy”, “How we Help” and “BESPOKE or ENTERPRISE?”). One clear main headline is easier for people and search engines.
Meta description is long (308 characters)
Your meta description is 308 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
167 internal links, 9 external
The homepage links to 167 pages on dezines.co.uk and 9 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.dezines.co.uk/.
Structured data in place
Structured data found: ProfessionalService 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://www.dezines.co.uk/sitemap.xml.
AI search readiness
4 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.
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 (1,449 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.dezines.co.uk/llms.txt (19 KiB, 88 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://www.dezines.co.uk/Store and https://www.dezines.co.uk/Store/Applications-c147777087 use the same meta description. A description written for each page earns more clicks.
4 pages without an H1
https://www.dezines.co.uk/Why-DEZINES, https://www.dezines.co.uk/DEZINES-Methodology, https://www.dezines.co.uk/DEZINES-Services and https://www.dezines.co.uk/Industries-we-Serve have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 61 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
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 400 ()”.
11 distorted images
11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
69 of 73 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,087 words of copy
The homepage carries about 1,087 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Buy Credit” and “Contact”.
10 calls to action
The homepage has 10 calls to action, for example “Buy Credit”, “Contact” and “Contact us”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 5 phone links and 5 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 2 of them by other companies (measured from a US location before any click).
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Termly
A consent management tool (Termly) 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 dezines.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on dezines.co.uk, including 17 speed issues, 4 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.