Website review, no card needed
misterspex.com website review
Visit site (opens in a new tab)Reviewed 31 October 202640 issues · 83 checks
This review found 40 issues worth fixing on misterspex.com, 10 of them high impact, across 83 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
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 168 ms |
| May 16, 2026 | 166 ms |
| May 23, 2026 | 166 ms |
| May 30, 2026 | 167 ms |
| Jun 6, 2026 | 168 ms |
| Jun 13, 2026 | 167 ms |
| Jun 20, 2026 | 167 ms |
| Jun 27, 2026 | 167 ms |
| Jul 4, 2026 | 166 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 164 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 166 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 168 ms |
| Sep 12, 2026 | 168 ms |
| Sep 19, 2026 | 168 ms |
| Sep 26, 2026 | 169 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 170 ms |
| Oct 17, 2026 | 170 ms |
| Oct 24, 2026 | 171 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.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Reduce unused JavaScript
2.0 s · 619 KiBAbout 619 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Render-blocking requests
1.6 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Kameleoon and Usercentrics CMP and others), adding 3.0 MB and 828 ms of main-thread time.
Use efficient cache lifetimes
350 ms · 455 KiB12 files are served with short cache lifetimes, so returning visitors download them again (455 KiB).
Improve image delivery
795 KiB8 images could be 795 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 533 ms
533 msGoogle Tag Manager costs a phone 533 ms of main-thread work and 378 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.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 284 ms. During a long task the page ignores taps.
2,065 HTML elements
The page has 2,065 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Kameleoon adds 160 ms
160 msKameleoon costs a phone 160 ms of main-thread work and 429 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.
Cloudinary adds 0 ms
0 msCloudinary costs a phone 0 ms of main-thread work and 1.9 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.
Legacy JavaScript
150 ms · 33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page. 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.
1 checks passed
Server response: 107 ms
107 msYour server sent the HTML in 107 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.
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 15.0 s
15.0 sThe page becomes fully interactive after 15.0 s. Good is under 3.8 s.
Speed Index: 8.8 s
8.8 sVisually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 642 ms
642 msScripts block taps and scrolling for 642 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 168 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 142 ms
142 msReal visitors wait 142 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.
Cumulative Layout Shift: 0.063
0.063The layout barely moves while loading (CLS 0.063, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 109 requests
3.8 MBYour homepage downloads 3.8 MB in 109 requests on a phone: images 2.3 MB (24), scripts 1.3 MB (49) and fonts 68 KiB (4). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Hero-Slider_1730x1194px_pg_default-2 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).
3 images far larger than shown
81 KiB3 images are downloaded at several times the size a phone draws them, for example hp-service-section-teaser_1312x1312px at 1,312 px wide, shown at 390 px. Resized copies would save about 81 KiB.
3 images below the first screen load straight away
3 images further down the page (344 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (363 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 1.1 g of CO₂ per visit
1.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 130.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Gut sehen & gut aussehen” and “Mister Spex – Dein Optiker mit persönlichem Servi…”). One clear main headline is easier for people and search engines.
Meta description is long (166 characters)
Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
213 internal links, 6 external
The homepage links to 213 pages on misterspex.com and 6 external pages.
5 checks passed
Title: 55 characters
Your title is a healthy 55 characters: “Mister Spex – Dein Optiker: Online und vor Ort im Store”.
Canonical URL set
The canonical URL is https://www.misterspex.de/.
Structured data in place
Structured data found: OnlineStore and WebSite.
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.misterspex.de/__service/product-browse-service/categories.xml.
AI search readiness
No llms.txt
There is no https://www.misterspex.de/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
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,272 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.misterspex.de/c/svc/857 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.misterspex.de/c/svc/857 has 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 143 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 27 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 “Access to font at 'https://d26hhearhq0yio.cloudfront.net/fonts/Roboto/Roboto-Light-webfont.woff' from origin 'https://w…”.
Missing source maps
Large scripts ship without source maps.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,155 words of copy
The homepage carries about 1,155 words of visible text.
2 checks passed
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 misterspex.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on misterspex.com, including 21 speed issues, 4 SEO issues and 5 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.