Website review, no card needed
signia-pro.com website review
Visit site (opens in a new tab)Reviewed 4 November 202633 issues · 78 checks
This review found 33 issues worth fixing on signia-pro.com, 13 of them high impact, across 78 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.8 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.7 s |
| Oct 31, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 118 ms |
| May 23, 2026 | 118 ms |
| May 30, 2026 | 117 ms |
| Jun 6, 2026 | 117 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 117 ms |
| Jul 4, 2026 | 118 ms |
| Jul 11, 2026 | 123 ms |
| Jul 18, 2026 | 125 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 124 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 123 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 125 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 126 ms |
| Oct 17, 2026 | 124 ms |
| Oct 24, 2026 | 124 ms |
| Oct 31, 2026 | 122 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.7 s
1.3 s
2.0 s
2.6 s
3.3 s
4.0 s
4.6 s
5.3 s
Speed
Render-blocking requests
3.5 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Reduce unused JavaScript
1.5 s · 307 KiBAbout 307 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Reduce unused CSS
1.4 s · 221 KiBAbout 221 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
150 ms · 1.4 MB26 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 210 ms. During a long task the page ignores taps.
6 third-party services on the page
6 third-party services load with your homepage (Optanon, New Relic and Browser-Update.org and others), adding 340 KiB and 89 ms of main-thread time.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Improve image delivery
15 KiB1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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: 108 ms
108 msYour server sent the HTML in 108 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: 9.9 s
9.9 sYour largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Women holding hearing aid Pure C&G MaX”.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 9.9 s
9.9 sThe page becomes fully interactive after 9.9 s. Good is under 3.8 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 360 ms
360 msScripts block taps and scrolling for 360 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.134
0.134The layout shifts by 0.134 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 118 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 122 ms
122 msReal visitors wait 122 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 15.0 MB in 69 requests
15.0 MBYour homepage downloads 15.0 MB in 69 requests on a phone: media 13.4 MB (1), scripts 865 KiB (24) and images 346 KiB (22). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
women-holding-ha-right-aligned-1920x1080.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 4.3 g of CO₂ per visit
4.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.25 g of CO₂e: 510.5 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
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
24 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 24 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Signia Pro - Hearing aid information for hearing care professionals”.
5 H1 headlines
There are 5 <h1> headlines (“Time to Live Noisy”, “Signia Multi-adaptive Xperience” and “Acoustic Intelligence™”). One clear main headline is easier for people and search engines.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
45 internal links, 5 external
The homepage links to 45 pages on signia-pro.com and 5 external pages.
6 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Signia Pro for Hearing Care Professionals. Explore our newest hearing aids, hearing aid technology, connectivity, acces…”.
Canonical URL set
The canonical URL is https://www.signia-pro.com/en/.
Structured data in place
Structured data found: Organization.
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.signia-pro.com/sitemap-cs-cz.xml.
AI search readiness
No llms.txt
There is no https://www.signia-pro.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.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (346 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.signia-pro.com/en/service/disclaimer is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://www.signia-pro.com/en all use the title “Signia Pro - Hearing aid information for hearing care professionals”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.signia-pro.com/en/signia-library, https://www.signia-pro.com/en/service/disclaimer, https://www.signia-pro.com/en/service/privacy-notice and https://www.signia-pro.com/en/service/corporate-information have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages with very little text
https://www.signia-pro.com/en/sustainability and https://www.signia-pro.com/en/service/corporate-information have 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 41 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
18 of 19 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 378 words of copy
The homepage carries about 378 words of visible text.
1 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Get in touch today” and “Contact”.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Analytics (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 signia-pro.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
- React
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on signia-pro.com, including 17 speed issues, 3 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.