Website review, no card needed
driftelement.com website review
Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 87 checks
This review found 26 issues worth fixing on driftelement.com, 9 of them high impact, across 87 checks. The most urgent: page weight: 9.0 MB in 323 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
88B- #5,626 of 117,615 reviewed websitesbeats 93%
- #3,103 of 66,923 online storesbeats 93%
- #3,008 of 61,018 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 172 ms |
| May 30, 2026 | 170 ms |
| Jun 6, 2026 | 172 ms |
| Jun 13, 2026 | 174 ms |
| Jun 20, 2026 | 173 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 178 ms |
| Jul 18, 2026 | 183 ms |
| Jul 25, 2026 | 180 ms |
| Aug 1, 2026 | 182 ms |
| Aug 8, 2026 | 187 ms |
| Aug 15, 2026 | 184 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 186 ms |
| Sep 5, 2026 | 182 ms |
| Sep 12, 2026 | 184 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 181 ms |
| Oct 24, 2026 | 183 ms |
| Oct 31, 2026 | 184 ms |
| Nov 7, 2026 | 180 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
0.6 s
1.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.4 s
5.0 s
Speed
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,104 HTML elements
The page has 3,104 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 72
72/100Your mobile performance score is 72. 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 (Klaviyo, Clarity and Shopify and others), adding 1.3 MB and 545 ms of main-thread time.
Reduce unused CSS
590 ms · 77 KiBAbout 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 590 ms faster on a phone.
Reduce unused JavaScript
486 KiBAbout 486 KiB of JavaScript is downloaded but never used on this page.
Shopify adds 86 ms
86 msShopify costs a phone 86 ms of main-thread work and 859 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
209 KiB9 images could be 209 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.
Render-blocking requests
100 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.
Use efficient cache lifetimes
66 KiB11 files are served with short cache lifetimes, so returning visitors download them again (66 KiB).
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 60 ms
60 msYour server sent the HTML in 60 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 15.1 s
15.1 sThe page becomes fully interactive after 15.1 s. Good is under 3.8 s.
Largest Contentful Paint: 6.4 s
6.4 sYour largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Adventskalender – Preise werden erhöht”.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 172 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 180 ms
180 msReal visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
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: 301 ms
301 msReal visitors wait 301 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 136 ms
136 msScripts block the page for only 136 ms while loading. Good is under 200 ms.
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.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 9.0 MB in 323 requests
9.0 MBYour homepage downloads 9.0 MB in 323 requests on a phone: media 5.7 MB (2), other files 1.2 MB (136) and scripts 1.0 MB (110). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Motorsport-Quarz-Rot-00001.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).
About 2.5 g of CO₂ per visit
2.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.54 g of CO₂e: 304.6 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
5 elements hidden from screen readers can still receive keyboard focus.
Scrollable region must have keyboard access (4 elements)
Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
36 links without text
36 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (8 elements)
ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 87 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
93 internal links, 21 external
The homepage links to 93 pages on driftelement.com and 21 external pages.
8 checks passed
Meta description: 91 characters
Your meta description is 91 characters: “DriftElement Rim Watches – Unique watches with authentic wheel rim design. Made in Germany.”.
One H1 headline
Your main headline reads: “@media screen and (max-width: 749px) { #HeaderSecondaryDesktopLogo { display: none !important; } } @media screen and (m…”.
Title: 64 characters
Your title is a healthy 64 characters: “DriftElement Rim Watches | Premium Watches with Wheel Rim Design”.
Canonical URL set
The canonical URL is https://www.driftelement.com/.
Structured data in place
Structured data found: 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://www.driftelement.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: 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,222 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.driftelement.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://www.driftelement.com/products/motorsport-rim-watch and https://www.driftelement.com/products/nitro-rim-watch use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.
7 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.
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 15 pages that loaded have a <title>.
Best practices
28 small tap targets
28 of 112 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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 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 417 words of copy
The homepage carries about 417 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact form” and “Where is my Order?”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 13 testimonial or review blocks, a star rating and “5628+ reviews”.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
25 cookies set on arrival
25Opening the homepage sets 25 cookies, 1 of them by other companies (measured from a US location before any click).
43 other companies contacted
Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 driftelement.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Teeinblue Product Personalizer · Eg Auto Add To Cart · Microsoft Clarity · Triplewhale · Judge Me Reviews · Forms · snapchat.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
Hiring
- Hiring
- 2 open roles
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on driftelement.com, including 11 speed 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.