Website review, no card needed
hpc.ag website review
Visit site (opens in a new tab)Reviewed 1 November 202620 issues · 72 checks
This review found 20 issues worth fixing on hpc.ag, 8 of them high impact, across 72 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Oct 3, 2026 | 99 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 117 ms |
| Oct 24, 2026 | 115 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.1 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 83
83/100Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
750 ms · 134 KiB1 image could be 134 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Reduce unused JavaScript
150 ms · 28 KiBAbout 28 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
15 KiBAbout 15 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 352 ms of it running JavaScript. That is comfortably low.
Server response: 122 ms
122 msYour server sent the HTML in 122 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 FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.0 s
3.0 sReal visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (3.4 s).
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 99 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user INP: 112 ms
112 msReal visitors wait 112 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.
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.4 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 3.6 s
3.6 sThe page is fully interactive after 3.6 s.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
2 images in older formats
2 images (152 KiB) 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.
1 image below the first screen load straight away
1 image further down the page (42 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.2 g of CO₂ per visit
0.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.19 g of CO₂e: 22.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 673 KiB in 42 requests
673 KiBYour homepage downloads 673 KiB in 42 requests on a phone: images 304 KiB (15), scripts 257 KiB (18) and HTML 47 KiB (1). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 30 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
65 internal links, 15 external
The homepage links to 65 pages on hpc.ag and 15 external pages.
8 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Spezialisiert auf Flächenrecycling, Umwelt und Sicherheit sowie Infrastruktur. Fordern Sie jetzt Ihr individuelles Ange…”.
One H1 headline
Your main headline reads: “Ihr Partner für Ingenieur- und Umweltprojekte”.
Title: 59 characters
Your title is a healthy 59 characters: “Ihr Partner für Ingenieurs- und Umweltprojekte – GINGER HPC”.
Canonical URL set
The canonical URL is https://gingerhpc.de/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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://gingerhpc.de/sitemap_index.xml.
AI search readiness
No llms.txt
There is no /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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (478 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages share a title
/leistungen/flaechenrecycling, /leistungen/umwelt-und-sicherheit, /leistungen/infrastruktur, /leistungen/flaechenrecycling/altlasten, /leistungen/flaechenrecycling/gebaeude and /leistungen/flaechenrecycling/entsorgungs-und-verwertungsmanagement and 1 other all use the title “Suchleiste einblenden”. Search engines can't tell which page to show for a search, so each competes with the others.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example /ueber-hpc, whose canonical is /ueber-ginger-hpc. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
/veranstaltungen, /referenzen, /leistungen, /karriere and /standorte have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
/veranstaltungen has 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.
1 page slow to respond
/karriere took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 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.
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
7 small tap targets
7 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 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.
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 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 738 words of copy
The homepage carries about 738 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Hotjar.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 checks passed
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 hpc.ag, 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
- Hosting
- netcup GmbH
Company
- Founded
- 1948
- Headquarters
- Harburg
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on hpc.ag, including 10 speed 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.