Website review, no card needed
adressa.no website review
Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 87 checks
This review found 45 issues worth fixing on adressa.no, 16 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 858 ms |
| May 23, 2026 | 853 ms |
| May 30, 2026 | 855 ms |
| Jun 6, 2026 | 844 ms |
| Jun 13, 2026 | 844 ms |
| Jun 20, 2026 | 842 ms |
| Jun 27, 2026 | 828 ms |
| Jul 4, 2026 | 827 ms |
| Jul 11, 2026 | 841 ms |
| Jul 18, 2026 | 862 ms |
| Jul 25, 2026 | 868 ms |
| Aug 1, 2026 | 881 ms |
| Aug 8, 2026 | 865 ms |
| Aug 15, 2026 | 847 ms |
| Aug 22, 2026 | 848 ms |
| Aug 29, 2026 | 864 ms |
| Sep 5, 2026 | 911 ms |
| Sep 12, 2026 | 927 ms |
| Sep 19, 2026 | 920 ms |
| Sep 26, 2026 | 890 ms |
| Oct 3, 2026 | 838 ms |
| Oct 10, 2026 | 823 ms |
| Oct 17, 2026 | 816 ms |
| Oct 24, 2026 | 825 ms |
| Oct 31, 2026 | 819 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 70 ms |
| May 23, 2026 | 70 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 72 ms |
| Jun 20, 2026 | 74 ms |
| Jun 27, 2026 | 76 ms |
| Jul 4, 2026 | 77 ms |
| Jul 11, 2026 | 77 ms |
| Jul 18, 2026 | 77 ms |
| Jul 25, 2026 | 77 ms |
| Aug 1, 2026 | 77 ms |
| Aug 8, 2026 | 77 ms |
| Aug 15, 2026 | 77 ms |
| Aug 22, 2026 | 77 ms |
| Aug 29, 2026 | 77 ms |
| Sep 5, 2026 | 78 ms |
| Sep 12, 2026 | 78 ms |
| Sep 19, 2026 | 78 ms |
| Sep 26, 2026 | 77 ms |
| Oct 3, 2026 | 77 ms |
| Oct 10, 2026 | 77 ms |
| Oct 17, 2026 | 77 ms |
| Oct 24, 2026 | 78 ms |
| Oct 31, 2026 | 77 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.3 s
2.5 s
3.8 s
5.1 s
6.3 s
7.6 s
8.9 s
10.1 s
Speed
Reduce unused JavaScript
1.7 s · 359 KiBAbout 359 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Render-blocking requests
1.9 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Font display
1.6 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).
Use efficient cache lifetimes
650 ms · 1,018 KiB29 files are served with short cache lifetimes, so returning visitors download them again (1,018 KiB).
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 139 KiBAbout 139 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.
Improve image delivery
350 ms · 140 KiB6 images could be 140 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 279 ms. During a long task the page ignores taps.
1,711 HTML elements
The page has 1,711 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
polarismedia.no adds 0 ms
0 mspolarismedia.no costs a phone 0 ms of main-thread work and 627 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.
Legacy JavaScript
200 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (JSDelivr CDN, medietall.no and k5a.io and others), adding 890 KiB and 43 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: 380 ms
380 msYour server sent the HTML in 380 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.6 s
12.6 sYour largest element takes 12.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 12.9 s
12.9 sThe page becomes fully interactive after 12.9 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 357 ms
357 msScripts block taps and scrolling for 357 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 70 ms to 77 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 0.7 s
0.7 sReal visitors wait 0.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 72 ms
72 msReal visitors wait 72 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: 0.4 s
0.4 sReal visitors see the first content after 0.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 256 ms
256 msReal visitors wait 256 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.083
0.083The layout barely moves while loading (CLS 0.083, good is under 0.1).
Images and page weight
Page weight: 2.9 MB in 101 requests
2.9 MBYour homepage downloads 2.9 MB in 101 requests on a phone: scripts 1.1 MB (34), media 811 KiB (4) and fonts 397 KiB (10). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
85 KiB1 image is downloaded at several times the size a phone draws it, for example 1e111629-22ae-35ef-b7a1-3337d23bad55 at 1,000 px wide, shown at 120 px. Resized copies would save about 85 KiB.
About 0.8 g of CO₂ per visit
0.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.82 g of CO₂e: 98.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
Images must have alternative text (3 elements)
Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
6 links inside paragraphs rely on colour alone to stand out.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Main landmark should not be contained in another landmark (108 elements)
Main landmark should not be contained in another landmark: 108 elements on the page fail this check, rated moderate 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 main landmark (1 element)
Document should not have more than one main 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.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Adressa - adressa.no”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
11 internal links, 16 external
The homepage links to 11 pages on adressa.no and 16 external pages.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Hold deg oppdatert med Midt-Norges og Trondheims største regionavis. Vi gir deg alltid de siste nyhetene innen innenrik…”.
One H1 headline
Your main headline reads: “adressa”.
Canonical URL set
The canonical URL is https://www.adressa.no/.
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.adressa.no/sitemaps/adresseavisen-root-sitemap.xml.
AI search readiness
robots.txt blocks 4 AI answer engine crawlers
4 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Most text only appears after JavaScript runs
20%A phone browser shows 1,181 words, but the HTML your server sends has only 233. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.adressa.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
Other pages
1 linked page hidden from search
https://www.adressa.no/nyheter/i/lVOBge/adresseavisens-rettigheter is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://www.adressa.no/nyheter all use the title “Adressa - adressa.no”. 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.adressa.no/nyheter, https://www.adressa.no/forbruker/i/66k4b8/kontakt-redaksjonen and https://www.adressa.no/nyheter/i/lVOBge/adresseavisens-rettigheter use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.adressa.no/forbruker/i/66k4b8/kontakt-redaksjonen, whose canonical is https://www.adressa.no/nytte/i/66k4b8/kontakt-redaksjonen. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.adressa.no/nyheter, https://www.adressa.no/sport, https://www.adressa.no/kultur and https://www.adressa.no/nytte have no <h1> headline, so visitors and search engines get no clear main topic.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
Every page has a meta description
All 9 pages that loaded have a meta description.
Every page has a title
All 9 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 (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
26 of 27 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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,181 words of copy
The homepage carries about 1,181 words of visible text.
1 checks passed
Direct contact links
Visitors can reach you directly: 6 phone links and 6 email links.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 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.
16 other companies contacted
Loading the homepage contacts 16 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 adressa.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
- Nuxt
- Hosting
- Globalconnect
Company
- Employees
- 241
- Founded
- 1767
- Headquarters
- Trondheim
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on adressa.no, including 17 speed issues, 3 SEO 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.