Website review, no card needed
silberline.com website review
Visit site (opens in a new tab)Reviewed 31 October 202644 issues · 86 checks
This review found 44 issues worth fixing on silberline.com, 17 of them high impact, across 86 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
69D- #101,131 of 117,615 reviewed websitesbeats 12%
- #61,456 of 66,923 online storesbeats 7%
- #465 of 711 Magento storesbeats 30%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 203 ms |
| May 16, 2026 | 206 ms |
| May 23, 2026 | 204 ms |
| May 30, 2026 | 203 ms |
| Jun 6, 2026 | 205 ms |
| Jun 13, 2026 | 200 ms |
| Jun 20, 2026 | 200 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 193 ms |
| Jul 18, 2026 | 194 ms |
| Jul 25, 2026 | 199 ms |
| Aug 1, 2026 | 205 ms |
| Aug 8, 2026 | 226 ms |
| Aug 15, 2026 | 231 ms |
| Aug 22, 2026 | 231 ms |
| Aug 29, 2026 | 229 ms |
| Sep 5, 2026 | 213 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 211 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 216 ms |
| Oct 10, 2026 | 217 ms |
| Oct 17, 2026 | 210 ms |
| Oct 24, 2026 | 205 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
Speed
Reduce unused JavaScript
2.6 s · 477 KiBAbout 477 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
thinglink.me adds 2.1 s
2.1 sthinglink.me costs a phone 2.1 s of main-thread work and 5.8 MB 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: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (thinglink.me, consentmanager.net and Thinglink and others), adding 6.0 MB and 2.7 s of main-thread time.
Improve image delivery
2.8 MB20 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
600 ms · 140 KiB14 files are served with short cache lifetimes, so returning visitors download them again (140 KiB).
Reduce unused CSS
600 ms · 119 KiBAbout 119 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 361 ms. During a long task the page ignores taps.
Render-blocking requests
350 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.
consentmanager.net adds 304 ms
304 msconsentmanager.net costs a phone 304 ms of main-thread work and 149 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.
Thinglink adds 270 ms
270 msThinglink costs a phone 270 ms of main-thread work and 43 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.
1,706 HTML elements
The page has 1,706 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
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: 128 ms
128 msYour server sent the HTML in 128 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: 24.8 s
24.8 sYour largest element takes 24.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “STANDART® PCUplus – Maximum Chemical Stability for Durable …”.
Time to Interactive: 29.9 s
29.9 sThe page becomes fully interactive after 29.9 s. Good is under 3.8 s.
First Contentful Paint: 7.3 s
7.3 sThe first text or image appears after 7.3 s on a phone. Good is under 1.8 s.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 986 ms
986 msScripts block taps and scrolling for 986 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 208 ms
208 msReal visitors wait 208 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
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
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 203 ms to 205 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.9 MB in 188 requests
9.9 MBYour homepage downloads 9.9 MB in 188 requests on a phone: images 8.0 MB (75), scripts 1.4 MB (87) and stylesheets 166 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
MET_Prismatic_100560_MA.jpg weighs 588 KiB. On a phone connection a single image that size takes seconds.
About 2.8 g of CO₂ per visit
2.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.81 g of CO₂e: 337.2 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
36 text elements with low contrast
36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (8 elements)
Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 85 images in the HTML carry an alt attribute.
52 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: 52 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
43 links with vague text
43 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “ECKART Effect Pigments – Innovative solutions for coatings, printing, and cosmetics”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
9 H1 headlines
There are 9 <h1> headlines (“STANDART® PCUplus – Maximum Chemical Stability fo…”, “ECKART Pearlescent Pigments:Made in Europe. Relia…” and “”). One clear main headline is easier for people and search engines.
Meta description is long (188 characters)
Your meta description is 188 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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
188 internal links, 15 external
The homepage links to 188 pages on silberline.com and 15 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.eckart.net/en/.
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.eckart.net/media/sitemap/sitemap_en.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.eckart.net/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,190 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://www.eckart.net/en/contact, https://www.eckart.net/en/locations/europe, https://www.eckart.net/en/productsearch, https://www.eckart.net/en/productsearch/general-industrial-coatings, https://www.eckart.net/en/productsearch/automotive-coatings and https://www.eckart.net/en/productsearch/powder-coatings and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.eckart.net/de/de, whose canonical is https://www.eckart.net/de. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 162 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.
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
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
151 of 178 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 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,002 words of copy
The homepage carries about 1,002 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: “Contact”.
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “LEARN MORE” and “CONTACT US”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 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.
2 checks passed
Consent tool: consentmanager
A consent management tool (consentmanager) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 silberline.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- E-commerce
- Magento
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on silberline.com, including 24 speed issues, 6 SEO issues and 2 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.