Website review, no card needed
drdiamondsmetacine.com website review
Visit site (opens in a new tab)Reviewed 21 November 202648 issues · 98 checks
This review found 48 issues worth fixing on drdiamondsmetacine.com, 16 of them high impact, across 98 checks. The most urgent: page weight: 102.0 MB in 700 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
70C- #105,111 of 126,357 reviewed websitesbeats 14%
- #63,225 of 70,445 online storesbeats 8%
- #58,381 of 63,948 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 925 ms |
| Nov 7, 2026 | 925 ms |
| Nov 14, 2026 | 928 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 167 ms |
| Jun 6, 2026 | 170 ms |
| Jun 13, 2026 | 181 ms |
| Jun 20, 2026 | 174 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 158 ms |
| Aug 1, 2026 | 168 ms |
| Aug 8, 2026 | 177 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 168 ms |
| Aug 29, 2026 | 163 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 151 ms |
| Oct 17, 2026 | 146 ms |
| Oct 24, 2026 | 139 ms |
| Oct 31, 2026 | 128 ms |
| Nov 7, 2026 | 121 ms |
| Nov 14, 2026 | 121 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
1.2 s
2.4 s
3.6 s
4.8 s
6.1 s
7.3 s
8.5 s
9.7 s
Speed
Main-thread work: 10.3 s
A phone's processor spends 10.3 s on main-thread work while loading, 5.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,857 HTML elements
The page has 4,857 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 (route.com, alia-prod.com and gotolstoy.com and others), adding 85.9 MB and 1.6 s of main-thread time.
Shopify adds 63 ms
63 msShopify costs a phone 63 ms of main-thread work and 82.6 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.
Use efficient cache lifetimes
900 ms · 1.5 MB35 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Reduce unused JavaScript
220 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 220 ms faster on a phone.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
route.com adds 445 ms
445 msroute.com costs a phone 445 ms of main-thread work and 1.1 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.
Duplicated JavaScript
486 KiB486 KiB JavaScript is shipped twice across bundles.
alia-prod.com adds 300 ms
300 msalia-prod.com costs a phone 300 ms of main-thread work and 546 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.
rebuyengine.com adds 229 ms
229 msrebuyengine.com costs a phone 229 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.
Improve image delivery
330 KiB6 images could be 330 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 233 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 88 KiBPolyfills for old browsers add 88 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
45 KiBAbout 45 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 19 ms
19 msYour server sent the HTML in 19 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.30
0.30For real visitors the layout shifts by 0.30 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 11.1 s
11.1 sYour largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image alt text not provided”.
Speed Index: 17.2 s
17.2 sVisually, the page fills in at 17.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 38.0 s
38.0 sThe page becomes fully interactive after 38.0 s. Good is under 3.8 s.
Total Blocking Time: 680 ms
680 msScripts block taps and scrolling for 680 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.258
0.258The layout shifts by 0.258 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 575 ms
575 msReal visitors wait 575 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 167 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 60% faster for real visitors
-60%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 102.0 MB in 700 requests
102.0 MBYour homepage downloads 102.0 MB in 700 requests on a phone: media 94.7 MB (8), scripts 3.1 MB (158) and other files 2.0 MB (414). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
a422481168ef40218ed709d231bb1ee5.thumbnail.0000000000.jpg 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).
2 images far larger than shown
143 KiB2 images are downloaded at several times the size a phone draws them, for example contour___lift_set_4x5__1___2.jpg at 1,230 px wide, shown at 120 px. Resized copies would save about 143 KiB.
4 images below the first screen load straight away
4 images further down the page (175 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 28.9 g of CO₂ per visit
28.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 28.90 g of CO₂e: 3468.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
22 tap targets too small
22 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (4 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 4 elements on the page fail this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 80 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (93 characters)
Your title is 93 characters, so Google will cut it off around 60: “Dr. Diamond Metacine: Luxury Clinical Skincare & Anti-Aging Formulas – Dr. Diamond's Meta…”.
Meta description is long (279 characters)
Your meta description is 279 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//drdiamondsmetacine.com/cdn/shop/files/logo-text-image…”.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
153 internal links, 3 external
The homepage links to 153 pages on drdiamondsmetacine.com and 3 external pages.
4 checks passed
One H1 headline
Your main headline reads: “The Metacine Cabinet”.
Canonical URL set
The canonical URL is https://drdiamondsmetacine.com/.
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://drdiamondsmetacine.com/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: 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 (2,142 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://drdiamondsmetacine.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://drdiamondsmetacine.com/apps/bubblehouse/rewards, https://drdiamondsmetacine.com/collections and https://drdiamondsmetacine.com/collections/all-sets have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://drdiamondsmetacine.com/products/eyelift-bioremodeling-peptide-multiplex and https://drdiamondsmetacine.com/products/the-contour-collection-duo use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://drdiamondsmetacine.com/products/instafacial%C2%AE-collection-discovery-set, whose canonical is https://drdiamondsmetacine.com/products/instafacial%c2%ae-collection-discovery-set. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://drdiamondsmetacine.com/apps/bubblehouse/rewards and https://drdiamondsmetacine.com/collections have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://drdiamondsmetacine.com/collections has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
4 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.
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://drdiamondsmetacine.com/.
37 small tap targets
37 of 87 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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: 108 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 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 1,470 words of copy
The homepage carries about 1,470 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: “JOIN LOYALTY FOR REWARDS.” and “SHOP NOW”.
34 calls to action
The homepage has 34 calls to action, for example “JOIN LOYALTY FOR REWARDS.”, “Shop Chevron Down” and “Shop All Arrow Diagonal”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 6 mores (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.
29 cookies set on arrival
29Opening the homepage sets 29 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.
71 other companies contacted
Loading the homepage contacts 71 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 drdiamondsmetacine.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 23 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Triplewhale · Mntn · Microsoft Clarity · Klaviyo Email Marketing Sms · Redo · Rebuy Personalization Engine · Tolstoy · Wyllo Formerly Nofraud · Yotpo Product Reviews · Userway Website Accessibility · Route Protection Tracking · Bubblehouse Dr Diamonds · Gdpr Cookie Consent · Polar Analytics · shareasale.com · nfcube.com · cloudfront.net · Selleasy · rebuyengine.com · gorgias.chat · metorik.com · 9gtb.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
- 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 48 issues on drdiamondsmetacine.com, including 20 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.