Website review, no card needed

thediary.com logo

thediary.com website review

Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 80 checks

This review found 33 issues worth fixing on thediary.com, 9 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.0 s1.7 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.3 s
Jun 27, 20262.5 s
Jul 4, 20262.6 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.6 s
Aug 22, 20262.5 s
Aug 29, 20262.2 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.0 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
165 ms133 msMay 16Oct 31161 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026138 ms
May 23, 2026138 ms
May 30, 2026138 ms
Jun 6, 2026137 ms
Jun 13, 2026137 ms
Jun 20, 2026137 ms
Jun 27, 2026137 ms
Jul 4, 2026139 ms
Jul 11, 2026142 ms
Jul 18, 2026144 ms
Jul 25, 2026148 ms
Aug 1, 2026151 ms
Aug 8, 2026154 ms
Aug 15, 2026153 ms
Aug 22, 2026153 ms
Aug 29, 2026153 ms
Sep 5, 2026148 ms
Sep 12, 2026149 ms
Sep 19, 2026146 ms
Sep 26, 2026147 ms
Oct 3, 2026149 ms
Oct 10, 2026154 ms
Oct 17, 2026161 ms
Oct 24, 2026161 ms
Oct 31, 2026161 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

Full-page screenshot of thediary.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thediary.com at 0.4 s0.4 s
  2. thediary.com at 0.8 s0.8 s
  3. thediary.com at 1.1 s1.1 s
  4. thediary.com at 1.5 s1.5 s
  5. thediary.com at 1.9 s1.9 s
  6. thediary.com at 2.3 s2.3 s
  7. thediary.com at 2.6 s2.6 s
  8. thediary.com at 3.0 s3.0 s

Speed

10 to fix56
  • Reduce unused JavaScript

    2.2 s · 345 KiB

    About 345 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. 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, Shopify and Clarity and others), adding 1.1 MB and 849 ms of main-thread time.

  • Use efficient cache lifetimes

    350 ms · 109 KiB

    17 files are served with short cache lifetimes, so returning visitors download them again (109 KiB).

  • Render-blocking requests

    450 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Improve image delivery

    350 ms · 98 KiB

    3 images could be 98 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Main-thread work: 3.7 s

    A phone's processor spends 3.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Tag Manager adds 233 ms

    233 ms

    Google Tag Manager costs a phone 233 ms of main-thread work and 322 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.

  • Shopify adds 177 ms

    177 ms

    Shopify costs a phone 177 ms of main-thread work and 384 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,718 HTML elements

    The page has 1,718 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    260 ms · 63 KiB

    About 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    38 KiB

    Polyfills for old browsers add 38 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: 37 ms

    37 ms

    Your server sent the HTML in 37 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • 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.

  • Largest Contentful Paint: 16.3 s

    16.3 s

    Your largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 16.3 s

    16.3 s

    The page becomes fully interactive after 16.3 s. Good is under 3.8 s.

  • Speed Index: 7.0 s

    7.0 s

    Visually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 3.2 s

    3.2 s

    The first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

  • Total Blocking Time: 314 ms

    314 ms

    Scripts block taps and scrolling for 314 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) got 17% slower for real visitors

    +17%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 138 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 147 ms

    147 ms

    Real visitors wait 147 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 360 ms

    360 ms

    Real visitors wait 360 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 21% faster for real visitors

    -21%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 288 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 288 requests on a phone: scripts 1.3 MB (90), other files 991 KiB (161) and images 589 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.89 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 106.7 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

5 to fixGoogle 8994
  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 4 links without text

    4 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 19 images in the HTML carry an alt attribute.

  • 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. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10088
  • Title is short (9 characters)

    Your title is only 9 characters: “DOAC Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (270 characters)

    Your meta description is 270 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 43 internal links, 11 external

    The homepage links to 43 pages on thediary.com and 11 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “The Diary”.

  • Canonical URL set

    The canonical URL is https://thediary.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization 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://thediary.com/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (829 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://thediary.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://thediary.com/products/the-growth-toolkit declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://thediary.com/products/the-growth-toolkit all use the title “DOAC Shop”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://thediary.com/collections/shop, https://thediary.com/pages/corporate-orders, https://thediary.com/collections/all, https://thediary.com/collections/the-cards, https://thediary.com/pages/faqs and https://thediary.com/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://thediary.com/pages/corporate-orders, https://thediary.com/pages/faqs and https://thediary.com/pages/contact 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 17 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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

2 to fixGoogle 9687
  • 9 small tap targets

    9 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://thediary.com/cdn/shop/t/43/assets/tiny.content.min.css?v=8365' because its MIME ty…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 5 testimonial or review blocks. 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 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 445 words of copy

    The homepage carries about 445 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 NOW”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “SHOP ALL”, “SHOP NOW” and “Shop The Diary”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies (measured from a US location before any click).

  • 50 other companies contacted

    Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 thediary.com, 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 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Intelligems A B Testing · Klaviyo Email Marketing Sms · Judge Me Reviews · Gorgias Live Chat Helpdesk · Pagefly Ai Page Builder · Microsoft Clarity · Sk Contact Form Builder · Triplewhale · Easylocation · Productiondeployment · Upcart · powr.io · trustpilot.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 Tag Manager | Hotjar | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Tucson

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 thediary.com, including 17 speed issues, 2 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25