Website review, no card needed
herningsholm.dk website review
Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 80 checks
This review found 34 issues worth fixing on herningsholm.dk, 15 of them high impact, across 80 checks. The most urgent: improve image delivery. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 165 ms |
| May 16, 2026 | 165 ms |
| May 23, 2026 | 168 ms |
| May 30, 2026 | 176 ms |
| Jun 6, 2026 | 182 ms |
| Jun 13, 2026 | 176 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 152 ms |
| Jul 11, 2026 | 156 ms |
| Jul 18, 2026 | 151 ms |
| Jul 25, 2026 | 157 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 151 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 165 ms |
| Sep 12, 2026 | 160 ms |
| Sep 19, 2026 | 161 ms |
| Sep 26, 2026 | 157 ms |
| Oct 3, 2026 | 156 ms |
| Oct 10, 2026 | 167 ms |
| Oct 17, 2026 | 167 ms |
| Oct 24, 2026 | 178 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.5 s
2.2 s
3.0 s
3.7 s
4.5 s
5.2 s
6.0 s
Speed
Improve image delivery
4.3 s · 957 KiB6 images could be 957 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.
Reduce unused JavaScript
2.3 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Use efficient cache lifetimes
9.0 MB8 files are served with short cache lifetimes, so returning visitors download them again (9.0 MB).
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 80). Pages that score under 90 lose visitors before the first paint.
Document request latency
384 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
2,329 HTML elements
The page has 2,329 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 849 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 203 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 34 KiBAbout 34 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.
1 third-party service on the page
1 third-party service load with your homepage (cookieinformation.com), adding 28 KiB and 35 ms of main-thread time.
Minify CSS
17 KiB17 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 80 but mobile only 54. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 545 ms
545 msYour server sent the HTML in 545 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: 18.6 s
18.6 sYour largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ved at trykke på 'Accepter alle' giver du samtykke til alle…”.
Time to Interactive: 18.8 s
18.8 sThe page becomes fully interactive after 18.8 s. Good is under 3.8 s.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Real-user INP: 244 ms
244 msReal visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 273 ms
273 msScripts block taps and scrolling for 273 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 165 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 790 ms
790 msReal visitors wait 790 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 12.9 MB in 144 requests
12.9 MBYour homepage downloads 12.9 MB in 144 requests on a phone: media 8.8 MB (2), images 1.4 MB (8) and other files 1.4 MB (86). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
jubilaeumsside.png weighs 844 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
513 KiB1 image is downloaded at several times the size a phone draws it, for example jubilaeumsside.png at 1,744 px wide, shown at 364 px. Resized copies would save about 513 KiB.
1 image in older formats
1 image (844 KiB) is 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.
About 3.7 g of CO₂ per visit
3.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.67 g of CO₂e: 439.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
[aria-*] attributes do not have valid values
[aria-*] attributes do not have valid values (1 element).
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
73 internal links, 14 external
The homepage links to 73 pages on herningsholm.dk and 14 external pages.
5 checks passed
One H1 headline
Your main headline reads: “For dig der er”.
Title: 56 characters
Your title is a healthy 56 characters: “For dig der vil - Herningsholm Erhvervsskole & Gymnasier”.
Canonical URL set
The canonical URL is https://www.herningsholm.dk/.
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.herningsholm.dk/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.herningsholm.dk/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 (903 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.herningsholm.dk/150 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
13 pages without a meta description
https://www.herningsholm.dk/soegning, https://www.herningsholm.dk/150, https://www.herningsholm.dk/eux, https://www.herningsholm.dk/10-klasse, https://www.herningsholm.dk/gymnasier/hhx-herning and https://www.herningsholm.dk/gymnasier/htx-herning and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.herningsholm.dk/soegning and https://www.herningsholm.dk/voksen-og-efteruddannelse have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.herningsholm.dk/soegning 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,279 words of copy
The homepage carries about 1,279 words of visible text.
2 checks passed
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
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 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 herningsholm.dk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Hosting
- Azure
Company
- Employees
- 430
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on herningsholm.dk, including 14 speed issues, 3 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.