Website review, no card needed

dylanoaks.com logo

dylanoaks.com website review

Visit site (opens in a new tab)Reviewed 8 November 202635 issues · 79 checks

This review found 35 issues worth fixing on dylanoaks.com, 8 of them high impact, across 79 checks. The most urgent: main-thread work: 10.9 s. 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
1.7 s1.5 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
174 ms142 msMay 16Oct 31153 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026162 ms
May 23, 2026159 ms
May 30, 2026159 ms
Jun 6, 2026155 ms
Jun 13, 2026156 ms
Jun 20, 2026154 ms
Jun 27, 2026155 ms
Jul 4, 2026158 ms
Jul 11, 2026156 ms
Jul 18, 2026159 ms
Jul 25, 2026159 ms
Aug 1, 2026157 ms
Aug 8, 2026160 ms
Aug 15, 2026161 ms
Aug 22, 2026161 ms
Aug 29, 2026163 ms
Sep 5, 2026170 ms
Sep 12, 2026169 ms
Sep 19, 2026160 ms
Sep 26, 2026155 ms
Oct 3, 2026148 ms
Oct 10, 2026146 ms
Oct 17, 2026149 ms
Oct 24, 2026149 ms
Oct 31, 2026153 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 dylanoaks.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dylanoaks.com at 1.1 s1.1 s
  2. dylanoaks.com at 2.2 s2.2 s
  3. dylanoaks.com at 3.2 s3.2 s
  4. dylanoaks.com at 4.3 s4.3 s
  5. dylanoaks.com at 5.4 s5.4 s
  6. dylanoaks.com at 6.5 s6.5 s
  7. dylanoaks.com at 7.6 s7.6 s
  8. dylanoaks.com at 8.6 s8.6 s

Speed

9 to fix50
  • Main-thread work: 10.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and heatmap.com and others), adding 1.4 MB and 1.4 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 563 KiB

    About 563 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    765 KiB

    21 images could be 765 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    600 ms

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

  • Google Tag Manager adds 504 ms

    504 ms

    Google Tag Manager costs a phone 504 ms of main-thread work and 476 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 264 ms

    264 ms

    Shopify costs a phone 264 ms of main-thread work and 543 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.

  • 2,907 HTML elements

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

  • 10 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 ms · 59 KiB

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

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 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: 45 ms

    45 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 31.3 s

    31.3 s

    Your largest element takes 31.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop Now”.

  • Time to Interactive: 37.0 s

    37.0 s

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

  • Speed Index: 11.9 s

    11.9 s

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

  • Total Blocking Time: 371 ms

    371 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 17 images without width and height

    17 images have no width and height attributes, so the layout jumps as each one loads.

  • Cumulative Layout Shift: 0.122

    0.122

    The layout shifts by 0.122 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

6 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.6 s

    1.6 s

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

  • Real-user INP: 155 ms

    155 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 336 ms

    336 ms

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

Images and page weight

3 to fix53
  • Page weight: 9.2 MB in 496 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 496 requests on a phone: images 3.7 MB (193), fonts 2.9 MB (4) and scripts 1.4 MB (97). Under 2 MB keeps phones on slow connections fast.

  • 9 images below the first screen load straight away

    9 images further down the page (718 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images far larger than shown

    376 KiB

    5 images are downloaded at several times the size a phone draws them, for example Tezza-4789.jpg at 2,660 px wide, shown at 350 px. Resized copies would save about 376 KiB.

  • 1 image in older formats

    1 image (41 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 2.6 g of CO₂ per visit

    2.62 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.62 g of CO₂e: 314.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

5 to fix78
  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • 12 tap targets too small

    12 tap targets are too small or too close together to hit reliably with a finger.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 text elements with low contrast

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

SEO

3 to fixGoogle 8584
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

  • 329 internal links, 6 external

    The homepage links to 329 pages on dylanoaks.com and 6 external pages.

6 checks passed
  • Meta description: 95 characters

    Your meta description is 95 characters: “Jewellery for every occasion. Look Good. Feel Confident. Buy yourself the jewel. #dylanoaksclub”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Dylan Oaks | Jewellery For Every Occasion | Official Store”.

  • Canonical URL set

    The canonical URL is https://www.dylanoaks.com/en-us.

  • 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.dylanoaks.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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 (2,336 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 11 pages without a meta description

    https://www.dylanoaks.com/en-us/collections/singles-day-matching-sets, https://www.dylanoaks.com/en-us/collections/forever-edit, https://www.dylanoaks.com/en-us/collections/new-in, https://www.dylanoaks.com/en-us/collections/charm-collection, https://www.dylanoaks.com/en-us/collections/engravable-necklaces and https://www.dylanoaks.com/en-us/collections/accessories and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.dylanoaks.com/en-us/collections/singles-day-matching-sets, https://www.dylanoaks.com/en-us/collections/forever-edit, https://www.dylanoaks.com/en-us/collections/new-in, https://www.dylanoaks.com/en-us/collections/charm-collection, https://www.dylanoaks.com/en-us/collections/engravable-necklaces and https://www.dylanoaks.com/en-us/collections/lisas-lust and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    https://www.dylanoaks.com/en-us/collections/forever-edit, https://www.dylanoaks.com/en-us/collections/new-in, https://www.dylanoaks.com/en-us/collections/charm-collection, https://www.dylanoaks.com/en-us/collections/engravable-necklaces, https://www.dylanoaks.com/en-us/collections/lisas-lust and https://www.dylanoaks.com/en-us/collections/accessories and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 89 found) and read each the way a search engine does.

5 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.

  • 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 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://www.dylanoaks.com/en-us.

  • 23 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 18 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.

  • About 735 words of copy

    The homepage carries about 735 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” and “LOGIN / REGISTER”.

  • 36 calls to action

    The homepage has 36 calls to action, for example “SHOP NOW”, “SHOP All New & Trending” and “SHOP All Necklaces”.

  • 4 short forms

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

  • Analytics in place

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

  • 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

1 to fix
  • 6 trackers load before any consent

    6

    Before 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.

  • 19 cookies set on arrival

    19

    Opening 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.

  • 33 other companies contacted

    Loading the homepage contacts 33 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 dylanoaks.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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Wishlist Hero · Microsoft Clarity · Loyalty Rewards And Referrals · Klaviyo Email Marketing Sms · Hulk Form Builder · Gdpr Cookie Consent · Tek Labs Gifts Upsell · loox.io · profitmetrics.io · socialsnowball.io

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 Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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 dylanoaks.com, including 16 speed issues, 3 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