Website review, no card needed
dagrofa.dk website review
Visit site (opens in a new tab)Reviewed 4 November 202625 issues · 81 checks
This review found 25 issues worth fixing on dagrofa.dk, 7 of them high impact, across 81 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 121 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 116 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 114 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 118 ms |
| Aug 29, 2026 | 119 ms |
| Sep 5, 2026 | 117 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 116 ms |
| Sep 26, 2026 | 115 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 118 ms |
| Oct 17, 2026 | 119 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 120 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.6 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Minify CSS
450 ms · 114 KiB114 KiB could be saved by minifying CSS.
Reduce unused CSS
450 ms · 108 KiBAbout 108 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
2,677 HTML elements
The page has 2,677 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 273 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
250 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Improve image delivery
211 KiB10 images could be 211 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
150 ms · 46 KiB46 KiB could be saved by minifying JavaScript.
Reduce unused JavaScript
150 ms · 44 KiBAbout 44 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (cookieinformation.com and hr-manager.net), adding 108 KiB and 45 ms of main-thread time.
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: 107 ms
107 msYour server sent the HTML in 107 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dagrofa.dk (drevet af Dagrofa ApS) bruger egne cookies og c…”.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 121 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 118 ms
118 msReal visitors wait 118 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 415 ms
415 msReal visitors wait 415 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 141 ms
141 msScripts block the page for only 141 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.068
0.068The layout barely moves while loading (CLS 0.068, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 75 requests
5.2 MBYour homepage downloads 5.2 MB in 75 requests on a phone: images 2.4 MB (39), media 2.1 MB (1) and fonts 280 KiB (6). Under 2 MB keeps phones on slow connections fast.
7 images far larger than shown
561 KiB7 images are downloaded at several times the size a phone draws them, for example 340f5883348213c447e4ba46738e4c5b-1-1.jpg at 1,280 px wide, shown at 199 px. Resized copies would save about 561 KiB.
An image on the first screen is lazy-loaded
Spar_Navbar-1.png 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).
7 images below the first screen load straight away
7 images further down the page (794 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (468 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.
About 1.5 g of CO₂ per visit
1.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 177.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
Form elements should have a visible label (2 elements)
Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
33 links without text
33 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 150 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Forside - Dagrofa”. Between 30 and 65 characters leaves room to say what you do and for whom.
154 internal links, 135 external
The homepage links to 154 pages on dagrofa.dk and 135 external pages.
7 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Dagrofa er en dansk fødevarekoncern med detailkæderne, Foodservice, logistik og Aarstiderne. Vi skaber madoplevelser fo…”.
One H1 headline
Your main headline reads: “madoplevelser”.
Canonical URL set
The canonical URL is https://www.dagrofa.dk/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.dagrofa.dk/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.dagrofa.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.
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 (3,290 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.dagrofa.dk/om-dagrofa/vores-vaerdier and https://www.dagrofa.dk/om-dagrofa/dagrofas-vaerdier-vores-maade-at-arbejde-paa all use the title “Kulturen i Dagrofa - Dagrofa”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.dagrofa.dk/om-dagrofa/vores-vaerdier and https://www.dagrofa.dk/om-dagrofa/dagrofas-vaerdier-vores-maade-at-arbejde-paa use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.dagrofa.dk/koncernstruktur, whose canonical is https://www.dagrofa.dk/om-dagrofa/koncernstruktur. 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 76 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 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”).
2 checks passed
Tap targets are thumb-sized
86 of 103 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 3,607 words of copy
The homepage carries about 3,607 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “En god start”.
1 call to action
The homepage has 1 call to action, for example “En god start”.
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks and 8 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 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.
2 other companies contacted
Loading the homepage contacts 2 hosts 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 dagrofa.dk, 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
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Hetzner
Company
- Employees
- 14,500
- Founded
- 1983
- Headquarters
- Ringsted
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on dagrofa.dk, including 10 speed issues and 1 SEO issue. 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.