Website review, no card needed
ampack.biz website review
Visit site (opens in a new tab)Reviewed 20 October 202632 issues · 85 checks
This review found 32 issues worth fixing on ampack.biz, 9 of them high impact, across 85 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
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| 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.5 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 118 ms |
| May 9, 2026 | 117 ms |
| May 16, 2026 | 117 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 134 ms |
| Jun 20, 2026 | 142 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 118 ms |
| Aug 15, 2026 | 122 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 119 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 118 ms |
| Oct 17, 2026 | 121 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
Render-blocking requests
1.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Improve image delivery
300 ms · 8.9 MB6 images could be 8.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 87
87/100Your mobile performance score is 87 (desktop: 98). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
620 ms · 243 KiBAbout 243 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 620 ms faster on a phone.
Google Tag Manager adds 247 ms
247 msGoogle Tag Manager costs a phone 247 ms of main-thread work and 347 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.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, cookiefirst.com and salesviewer.org and others), adding 443 KiB and 259 ms of main-thread time.
Legacy JavaScript
250 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
150 ms · 26 KiBAbout 26 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 116 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
5 KiB1 file is served with short cache lifetimes, so returning visitors download them again (5 KiB).
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.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 418 ms of it running JavaScript. That is comfortably low.
Server response: 65 ms
65 msYour server sent the HTML in 65 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.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: 6.6 s
6.6 sThe page becomes fully interactive after 6.6 s. Good is under 3.8 s.
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 118 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (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: 641 ms
641 msReal visitors wait 641 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 61 ms
61 msScripts block the page for only 61 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 10.0 MB in 33 requests
10.0 MBYour homepage downloads 10.0 MB in 33 requests on a phone: images 9.2 MB (11), scripts 576 KiB (9) and fonts 175 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
News-Bild_2500x5000_alle.jpg weighs 8.7 MB. On a phone connection a single image that size takes seconds.
4 images in older formats
4 images (8.9 MB) are 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.
5 images below the first screen load straight away
5 images further down the page (8.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.8 g of CO₂ per visit
2.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.84 g of CO₂e: 340.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
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.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
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 17 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 8 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (184 characters)
Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
145 internal links, 11 external
The homepage links to 145 pages on ampack.biz and 11 external pages.
5 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Ampack - The building shell experts. Since 1946.: Ampack”.
Canonical URL set
The canonical URL is https://www.ampack.biz/eu-en/.
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.ampack.biz/sitemap_index.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.ampack.biz/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 (404 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages share 3 titles
https://www.ampack.biz/ch-de, https://www.ampack.biz/at-de and https://www.ampack.biz/de-de all use the title “Ampack - Die Experten der Gebäudehülle. Seit 1946.: Ampack”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages share a meta description
https://www.ampack.biz/ch-de, https://www.ampack.biz/at-de and https://www.ampack.biz/de-de use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://www.ampack.biz/ch-de, https://www.ampack.biz/ch-fr, https://www.ampack.biz/ch-it, https://www.ampack.biz/at-de, https://www.ampack.biz/de-de and https://www.ampack.biz/fr-fr and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.ampack.biz/eu-en/products/membranes/vapour-checks took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 57 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
35 small tap targets
35 of 51 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
About 320 words of copy
The homepage carries about 320 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Download centre” and “Contact”.
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Download centre” and “Download”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
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.
7 other companies contacted
Loading the homepage contacts 7 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 ampack.biz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- TYPO3 CMS
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on ampack.biz, including 9 speed issues, 4 SEO 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.