Website review, no card needed
dr-fischer.com website review
Visit site (opens in a new tab)Reviewed 20 November 202648 issues · 98 checks
This review found 48 issues worth fixing on dr-fischer.com, 23 of them high impact, across 98 checks. The most urgent: render-blocking 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
68D- #109,734 of 125,141 reviewed websitesbeats 10%
- #65,324 of 70,110 online storesbeats 5%
- #2,473 of 2,939 WooCommerce storesbeats 12%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.5 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 4.2 s |
| Oct 31, 2026 | 4.2 s |
| Nov 7, 2026 | 4.2 s |
| Nov 14, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 156 ms |
| Jun 6, 2026 | 170 ms |
| Jun 13, 2026 | 199 ms |
| Jun 20, 2026 | 198 ms |
| Jun 27, 2026 | 199 ms |
| Jul 4, 2026 | 193 ms |
| Jul 11, 2026 | 178 ms |
| Jul 18, 2026 | 184 ms |
| Jul 25, 2026 | 181 ms |
| Aug 1, 2026 | 166 ms |
| Aug 8, 2026 | 157 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 160 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 173 ms |
| Oct 24, 2026 | 163 ms |
| Oct 31, 2026 | 160 ms |
| Nov 7, 2026 | 162 ms |
| Nov 14, 2026 | 155 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.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.8 s
9.1 s
10.3 s
Speed
Render-blocking requests
5.3 s142 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.3 s.
Google Tag Manager adds 1.3 s
1.3 sGoogle Tag Manager costs a phone 1.3 s of main-thread work and 799 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 10.0 s
A phone's processor spends 10.0 s on main-thread work while loading, 4.9 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, Google CDN and Hotjar and others), adding 2.0 MB and 3.3 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google CDN adds 674 ms
674 msGoogle CDN costs a phone 674 ms of main-thread work and 742 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 618 ms. During a long task the page ignores taps.
Reduce unused CSS
450 ms · 148 KiBAbout 148 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Hotjar adds 515 ms
515 msHotjar costs a phone 515 ms of main-thread work and 65 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.
TikTok adds 283 ms
283 msTikTok costs a phone 283 ms of main-thread work and 152 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,272 HTML elements
The page has 2,272 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
250 ms · 60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Duplicated JavaScript
250 ms · 38 KiB38 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 250 ms faster on a phone.
Use efficient cache lifetimes
205 KiB10 files are served with short cache lifetimes, so returning visitors download them again (205 KiB).
Minify JavaScript
150 ms · 17 KiB17 KiB could be saved by minifying JavaScript.
Improve image delivery
164 KiB1 image could be 164 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 104 ms
104 msYour server sent the HTML in 104 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 LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.1 s
3.1 sReal visitors wait 3.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 27.5 s
27.5 sThe page becomes fully interactive after 27.5 s. Good is under 3.8 s.
Speed Index: 13.9 s
13.9 sVisually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 3.3 s
3.3 sScripts block taps and scrolling for 3.3 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 6.9 s
6.9 sYour largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 156 ms to 155 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-11-14, real Chrome visitors' largest content (lcp) went from 3.8 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 153 ms
153 msReal visitors wait 153 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 242 requests
5.1 MBYour homepage downloads 5.1 MB in 242 requests on a phone: scripts 2.5 MB (114), images 1.5 MB (16) and fonts 410 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 174.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 12 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (172 characters)
Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
14 links with vague text
14 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
354 internal links, 30 external
The homepage links to 354 pages on dr-fischer.com and 30 external pages.
5 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Dr. Fischer – tried & tested - A Worldwide trusted brand”.
Canonical URL set
The canonical URL is https://www.dr-fischer.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.dr-fischer.com/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no https://www.dr-fischer.com/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.
2 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 (1,495 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 113 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
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 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
39 of 45 tappable elements near the top are at least 24 px.
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.
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.
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 812 words of copy
The homepage carries about 812 words of visible text.
5 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Learn More”, “Contact Us” and “Sign Up”.
4 short forms
4 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 68 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
7 trackers load before any consent
7Before 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). 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, 1 of them by other companies (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.
25 other companies contacted
Loading the homepage contacts 25 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 dr-fischer.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- DigitalOcean
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 dr-fischer.com, including 21 speed issues, 5 SEO issues and 3 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.