Website review, no card needed
apotek1.no website review
Visit site (opens in a new tab)Reviewed 18 November 202630 issues · 58 checks
This review found 30 issues worth fixing on apotek1.no, 11 of them high impact, across 58 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.0 s |
| Nov 7, 2026 | 3.1 s |
| Nov 14, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 170 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 171 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 171 ms |
| Jul 25, 2026 | 173 ms |
| Aug 1, 2026 | 173 ms |
| Aug 8, 2026 | 172 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 170 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 170 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 169 ms |
| Oct 3, 2026 | 168 ms |
| Oct 10, 2026 | 166 ms |
| Oct 17, 2026 | 168 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 170 ms |
| Nov 7, 2026 | 171 ms |
| Nov 14, 2026 | 172 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.73
0.73For real visitors the layout shifts by 0.73 (75th percentile). Good is under 0.1.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 170 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 171 ms
171 msReal visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 467 ms
467 msReal visitors wait 467 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 6.6 MB
6.6 MBYour homepage downloads 6.6 MB on a phone, 3.1 MB of it images (46%). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.
10 images below the first screen load straight away
10 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
9 images in older formats
9 images (907 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.
9 images far larger than shown
297 KiB9 images are downloaded at several times the size a phone draws them, for example RX-banner-ikon-mere-space-900x900.png at 900 px wide, shown at 190 px. Resized copies would save about 297 KiB.
About 1.9 g of CO₂ per visit
1.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.87 g of CO₂e: 224.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
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
49 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: 49 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (8 characters)
Your title is only 8 characters: “Apotek 1”. 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.
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 (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.
11 internal links, 0 external
The homepage links to 11 pages on apotek1.no and 0 external pages.
2 checks passed
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.apotek1.no/feed/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
8%A phone browser shows 913 words, but the HTML your server sends has only 69. 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.apotek1.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.
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
10 pages share a title
/, https://www.apotek1.no/medlem, https://www.apotek1.no/tilbud, https://www.apotek1.no/varemerker, https://www.apotek1.no/raad-og-tips and https://www.apotek1.no/vaare-apotek and 4 others all use the title “Apotek 1”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://www.apotek1.no/medlem, https://www.apotek1.no/tilbud, https://www.apotek1.no/varemerker, https://www.apotek1.no/raad-og-tips, https://www.apotek1.no/vaare-apotek and https://www.apotek1.no/kundesenter and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://www.apotek1.no/medlem, https://www.apotek1.no/tilbud, https://www.apotek1.no/varemerker, https://www.apotek1.no/raad-og-tips, https://www.apotek1.no/vaare-apotek and https://www.apotek1.no/kundesenter and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://www.apotek1.no/medlem, https://www.apotek1.no/tilbud, https://www.apotek1.no/varemerker, https://www.apotek1.no/raad-og-tips, https://www.apotek1.no/vaare-apotek and https://www.apotek1.no/kundesenter and 3 others have 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.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 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 “Access to XMLHttpRequest at 'https://static.lipscore.com/assets/lipscore-v1-2e2951a46c8bf29aa4ba34b7e15ecba509a9e089b6c…”.
2 checks passed
Tap targets are thumb-sized
65 of 70 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.
Thin social proof
Social proof on the homepage: 1 trust badge. 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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 913 words of copy
The homepage carries about 913 words of visible text.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 apotek1.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
- AWS
Company
- Founded
- 1999
- Headquarters
- Lørenskog
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on apotek1.no, including 3 speed issues, 6 SEO issues and 5 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.