Website review, no card needed
aarstiderne.com website review
Visit site (opens in a new tab)Reviewed 20 October 202641 issues · 87 checks
This review found 41 issues worth fixing on aarstiderne.com, 13 of them high impact, across 87 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 155 ms |
| May 9, 2026 | 154 ms |
| May 16, 2026 | 154 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 156 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 172 ms |
| Jul 4, 2026 | 177 ms |
| Jul 11, 2026 | 174 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 166 ms |
| Aug 15, 2026 | 166 ms |
| Aug 22, 2026 | 165 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 170 ms |
| Sep 19, 2026 | 172 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 177 ms |
| Oct 17, 2026 | 176 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.8 s
1.6 s
2.4 s
3.2 s
3.9 s
4.7 s
5.5 s
6.3 s
Speed
Improve image delivery
2.1 s · 6.7 MB13 images could be 6.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
Use efficient cache lifetimes
4.8 s · 885 KiB34 files are served with short cache lifetimes, so returning visitors download them again (885 KiB).
Render-blocking requests
2.4 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Reduce unused JavaScript
1.8 s · 428 KiBAbout 428 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
3,594 HTML elements
The page has 3,594 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 87). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 97 KiBAbout 97 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
run.app adds 166 ms
166 msrun.app costs a phone 166 ms of main-thread work and 672 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.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 511 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (run.app, dialogintelligens.dk and puzzel.com and others), adding 867 KiB and 304 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 111 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 87 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 407 ms
407 msYour server sent the HTML in 407 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: 14.1 s
14.1 sYour largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aarstiderne bruger egne cookies og lagrer data med henblik …”.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.3 s
14.3 sThe page becomes fully interactive after 14.3 s. Good is under 3.8 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.11
0.11The layout shifts by 0.11 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 155 ms to 176 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 172 ms
172 msReal visitors wait 172 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.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 114 ms
114 msScripts block the page for only 114 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 10.4 MB in 100 requests
10.4 MBYour homepage downloads 10.4 MB in 100 requests on a phone: images 9.0 MB (51), scripts 1.2 MB (21) and stylesheets 117 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (248 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.
2 images below the first screen load straight away
2 images further down the page (276 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.0 g of CO₂ per visit
2.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.95 g of CO₂e: 354.5 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
Elements must only use permitted ARIA attributes (4 elements)
Elements must only use permitted ARIA attributes: 4 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.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 40 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Tag med til Asien på fredag” and “MiniMåltidskasser”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.aarstiderne.com/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
90 internal links, 12 external
The homepage links to 90 pages on aarstiderne.com and 12 external pages.
3 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “Aarstiderne er 100% økologisk og har et stort udvalg af måltidskasser samt frugtkasser, grønt, og dagligvarer.”.
Title: 54 characters
Your title is a healthy 54 characters: “Økologiske måltidskasser, frugt, grønt og dagligvarer.”.
robots.txt in place
robots.txt is in place.
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.
Some text only appears after JavaScript runs
39%The HTML your server sends has 1,394 of the 3,598 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.aarstiderne.com/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.
1 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.
Other pages
1 linked page hidden from search
https://www.aarstiderne.com/kurv is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages share a title
https://www.aarstiderne.com/find-din-maaltidskasse, https://www.aarstiderne.com/find-din-maaltidskasse/god-weekend and https://www.aarstiderne.com/find-din-maaltidskasse/lynhurtige-livretter all use the title “Find din måltidskasse til 1, 2, 3, 4 eller 5 personer”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://www.aarstiderne.com/find-din-maaltidskasse, https://www.aarstiderne.com/find-din-maaltidskasse/god-weekend and https://www.aarstiderne.com/find-din-maaltidskasse/lynhurtige-livretter use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.aarstiderne.com/soegeresultater, https://www.aarstiderne.com/fordele/bliv-kunde and https://www.aarstiderne.com/kundeservice have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.aarstiderne.com/dagligvarer/weekend 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.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 13 pages that loaded have a meta description.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “checkState is not defined o.showCookieBanner [as showBanner] (<anonymous>:105:5)”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
133 of 144 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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,598 words of copy
The homepage carries about 3,598 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Start måltidskasse-guiden”.
4 short forms
4 short forms (4 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Ads (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (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.
11 other companies contacted
Loading the homepage contacts 11 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 aarstiderne.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
Company
- Employees
- 350
- Founded
- 1988
- Headquarters
- Barrit
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on aarstiderne.com, including 18 speed issues, 5 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.