Website review, no card needed
tax-free.no website review
Visit site (opens in a new tab)Reviewed 2 November 202642 issues · 91 checks
This review found 42 issues worth fixing on tax-free.no, 15 of them high impact, across 91 checks. The most urgent: page weight: 60.9 MB in 408 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 200 ms |
| May 23, 2026 | 202 ms |
| May 30, 2026 | 202 ms |
| Jun 6, 2026 | 202 ms |
| Jun 13, 2026 | 197 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 186 ms |
| Jul 11, 2026 | 183 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 192 ms |
| Aug 1, 2026 | 195 ms |
| Aug 8, 2026 | 199 ms |
| Aug 15, 2026 | 203 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 203 ms |
| Sep 5, 2026 | 202 ms |
| Sep 12, 2026 | 202 ms |
| Sep 19, 2026 | 203 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 208 ms |
| Oct 17, 2026 | 205 ms |
| Oct 24, 2026 | 206 ms |
| Oct 31, 2026 | 210 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
1.5 s
2.9 s
4.4 s
5.9 s
7.3 s
8.8 s
10.3 s
11.7 s
Speed
Main-thread work: 10.7 s
A phone's processor spends 10.7 s on main-thread work while loading, 5.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,931 HTML elements
The page has 3,931 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (bambuser.com, Google Tag Manager and kundo.se and others), adding 2.3 MB and 1.7 s of main-thread time.
Reduce unused JavaScript
824 KiBAbout 824 KiB of JavaScript is downloaded but never used on this page.
bambuser.com adds 694 ms
694 msbambuser.com costs a phone 694 ms of main-thread work and 643 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.
Google Tag Manager adds 571 ms
571 msGoogle Tag Manager costs a phone 571 ms of main-thread work and 671 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 386 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
368 KiB27 files are served with short cache lifetimes, so returning visitors download them again (368 KiB).
kundo.se adds 202 ms
202 mskundo.se costs a phone 202 ms of main-thread work and 326 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.
bambuser.net adds 89 ms
89 msbambuser.net costs a phone 89 ms of main-thread work and 302 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.
Improve image delivery
150 ms · 180 KiB13 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 43 KiBAbout 43 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify JavaScript
57 KiB57 KiB could be saved by minifying JavaScript.
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: 280 ms
280 msYour server sent the HTML in 280 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 CLS: 0.72
0.72For real visitors the layout shifts by 0.72 (75th percentile). Good is under 0.1.
Time to Interactive: 26.9 s
26.9 sThe page becomes fully interactive after 26.9 s. Good is under 3.8 s.
Speed Index: 12.9 s
12.9 sVisually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s.
Real-user INP: 252 ms
252 msReal visitors wait 252 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 200 ms to 210 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 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.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 60.9 MB in 408 requests
60.9 MBYour homepage downloads 60.9 MB in 408 requests on a phone: media 56.2 MB (14), scripts 2.7 MB (200) and images 1.2 MB (83). Under 2 MB keeps phones on slow connections fast.
About 17.2 g of CO₂ per visit
17.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 17.25 g of CO₂e: 2070.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h2 → h4), 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. (15 elements).
2 checks passed
Every image has alt text
All 58 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 2 mores 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.
Structured data has 8 problems
Structured data found ((untyped) and BreadcrumbList) but with 8 problems, for example “untyped block: missing @context (expected "https://schema.org")”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
249 internal links, 3 external
The homepage links to 249 pages on tax-free.no and 3 external pages.
5 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Norges største Tax-free butikk. Kjøp vin, øl, godteri, men også hudpleie, parfyme og sminke. Forhåndsbestill med Klikk …”.
Title: 56 characters
Your title is a healthy 56 characters: “Tax Free - online shopping for flypassasjerer | Tax Free”.
Canonical URL set
The canonical URL is https://www.tax-free.no/no/.
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.tax-free.no/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.tax-free.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.
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 (792 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.tax-free.no/no/category940/beauty and https://www.tax-free.no/category940/beauty all use the title “Beauty | Parfyme, hudpleie og makeup | Tax Free”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://www.tax-free.no/no/klikk-hent, https://www.tax-free.no/no/lojalitet, https://www.tax-free.no/no/live-shopping, https://www.tax-free.no/no/tips-og-trender, https://www.tax-free.no/no/wishlists and https://www.tax-free.no/no/kundeservice have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.tax-free.no/no/category940/beauty and https://www.tax-free.no/category940/beauty use the same meta description. A description written for each page earns more clicks.
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.tax-free.no/category940/beauty, whose canonical is https://www.tax-free.no/no/category940/beauty. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages slow to respond
https://www.tax-free.no/no/live-shopping, https://www.tax-free.no/category940/beauty, https://www.tax-free.no/category10/beauty/parfyme, https://www.tax-free.no/category11/beauty/parfyme/parfyme-dame and https://www.tax-free.no/category138/beauty/makeup took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 175 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 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'addEventListener')”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
50 of 50 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.
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 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 461 words of copy
The homepage carries about 461 words of visible text.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 2 trust badges.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
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 tax-free.no, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on tax-free.no, including 20 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.