Website review, no card needed
collinsdebden.us website review
Visit site (opens in a new tab)Reviewed 8 November 202639 issues · 78 checks
This review found 39 issues worth fixing on collinsdebden.us, 16 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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
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.6 s
6.6 s
7.5 s
Speed
Reduce unused JavaScript
3.6 s · 905 KiBAbout 905 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Use efficient cache lifetimes
1.0 s · 306 KiB12 files are served with short cache lifetimes, so returning visitors download them again (306 KiB).
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.0 s
A phone's processor spends 8.0 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,098 HTML elements
The page has 4,098 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (hcaptcha.com, YouTube and Shopify and others), adding 4.2 MB and 1.6 s of main-thread time.
hcaptcha.com adds 886 ms
886 mshcaptcha.com costs a phone 886 ms of main-thread work and 1.2 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.
Improve image delivery
930 KiB2 images could be 930 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
580 ms · 155 KiBAbout 155 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 580 ms faster on a phone.
YouTube adds 454 ms
454 msYouTube costs a phone 454 ms of main-thread work and 987 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.
Render-blocking requests
300 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Shopify adds 177 ms
177 msShopify costs a phone 177 ms of main-thread work and 1.0 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.
seguno.com adds 81 ms
81 msseguno.com costs a phone 81 ms of main-thread work and 994 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.
Legacy JavaScript
150 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.1 s
22.1 sYour largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 31.5 s
31.5 sThe page becomes fully interactive after 31.5 s. Good is under 3.8 s.
First Contentful Paint: 6.4 s
6.4 sThe first text or image appears after 6.4 s on a phone. Good is under 1.8 s.
Speed Index: 12.2 s
12.2 sVisually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 524 ms
524 msScripts block taps and scrolling for 524 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
Cumulative Layout Shift: 0.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
Images and page weight
Page weight: 7.1 MB in 479 requests
7.1 MBYour homepage downloads 7.1 MB in 479 requests on a phone: images 2.4 MB (103), scripts 2.3 MB (138) and other files 1.2 MB (210). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Copy_of_EDM_Headers_-_2026-08-20T150150.496.png 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 2.0 g of CO₂ per visit
2.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.00 g of CO₂e: 240.1 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
Hidden but focusable
26 elements hidden from screen readers can still receive keyboard focus.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
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 248 images in the HTML carry an alt attribute.
46 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: 46 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is short (48 characters)
Your meta description is only 48 characters: “The world's leading Diary & Stationery Supplier.”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//collinsdebden.us/cdn/shop/files/Collins_Logo.png?v=16…”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
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.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
243 internal links, 7 external
The homepage links to 243 pages on collinsdebden.us and 7 external pages.
4 checks passed
Title: 37 characters
Your title is a healthy 37 characters: “Collins Debden US – US Collins Debden”.
Canonical URL set
The canonical URL is https://collinsdebden.us/.
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://collinsdebden.us/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,291 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://collinsdebden.us/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://collinsdebden.us/collections/diaries, https://collinsdebden.us/collections/diaries-business-diaries, https://collinsdebden.us/collections/diaries-fashion-diaries, https://collinsdebden.us/collections/diaries-edge, https://collinsdebden.us/collections/diaries-essentials and https://collinsdebden.us/collections/scandi and 8 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 58 found) and read each the way a search engine does.
6 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
9 of 9 tappable elements near the top are at least 24 px.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
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 959 words of copy
The homepage carries about 959 words of visible text.
2 checks passed
7 calls to action
The homepage has 7 calls to action, for example “SHOP NOW”, “Subscribe” and “Contact Us”.
41 short forms
41 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Ads (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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies, 1 of them by other companies (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.
19 other companies contacted
Loading the homepage contacts 19 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 collinsdebden.us, 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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Seguno Popups · Restockrocket · Selleasy
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on collinsdebden.us, including 19 speed issues, 5 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.