Website review, no card needed
pharmadrops.dk website review
Visit site (opens in a new tab)Reviewed 16 November 202632 issues · 79 checks
This review found 32 issues worth fixing on pharmadrops.dk, 11 of them high impact, across 79 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.2 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 196 ms |
| Jun 6, 2026 | 205 ms |
| Jun 13, 2026 | 209 ms |
| Jun 20, 2026 | 212 ms |
| Jun 27, 2026 | 222 ms |
| Jul 4, 2026 | 209 ms |
| Jul 11, 2026 | 205 ms |
| Jul 18, 2026 | 221 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 205 ms |
| Aug 8, 2026 | 236 ms |
| Aug 15, 2026 | 238 ms |
| Aug 22, 2026 | 240 ms |
| Aug 29, 2026 | 236 ms |
| Sep 5, 2026 | 224 ms |
| Sep 12, 2026 | 214 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 220 ms |
| Oct 3, 2026 | 223 ms |
| Oct 10, 2026 | 236 ms |
| Oct 17, 2026 | 257 ms |
| Oct 24, 2026 | 262 ms |
| Oct 31, 2026 | 237 ms |
| Nov 7, 2026 | 225 ms |
| Nov 14, 2026 | 209 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
2.1 s
4.2 s
6.4 s
8.5 s
10.6 s
12.7 s
14.9 s
17.0 s
Speed
Reduce unused JavaScript
2.1 s · 690 KiBAbout 690 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Improve image delivery
1.4 s · 818 KiB17 images could be 818 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.1 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
300 ms · 49 KiBAbout 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,996 HTML elements
The page has 1,996 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
7 third-party services on the page
7 third-party services load with your homepage (Cloudflare, Clarity and Google Fonts and others), adding 140 KiB and 30 ms of main-thread time.
Use efficient cache lifetimes
17 KiB14 files are served with short cache lifetimes, so returning visitors download them again (17 KiB).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 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: 10.2 s
10.2 sYour largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 17.5 s
17.5 sVisually, the page fills in at 17.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 12.7 s
12.7 sThe page becomes fully interactive after 12.7 s. Good is under 3.8 s.
Real-user INP: 209 ms
209 msReal visitors wait 209 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 597 ms
597 msScripts block taps and scrolling for 597 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.123
0.123The layout shifts by 0.123 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 196 ms to 209 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 CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
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.
Real-user TTFB: 486 ms
486 msReal visitors wait 486 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 40% faster for real visitors
-40%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 3.0 MB in 328 requests
3.0 MBYour homepage downloads 3.0 MB in 328 requests on a phone: scripts 1.6 MB (212), images 1.1 MB (35) and other files 206 KiB (78). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 102.3 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
60 text elements with low contrast
60 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 73 images in the HTML carry an alt attribute.
13 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 13 WCAG 2.2 A/AA and best-practice rules on the phone render: 13 passed and 0 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Findroenigen”, “Black Month” and “Black Month”). One clear main headline is easier for people and search engines.
79 internal links, 2 external
The homepage links to 79 pages on pharmadrops.dk and 2 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Køb dansk fuldspektret CBD olie hos Pharmadrops. Labtestet, 10/20/30% styrke, fri fragt over beløbsgrænsen og hurtig le…”.
Title: 53 characters
Your title is a healthy 53 characters: “CBD Olie i Høj Kvalitet – Dansk Webshop | Pharmadrops”.
Canonical URL set
The canonical URL is https://pharmadrops.dk/.
Structured data in place
Structured data found: FAQPage.
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://pharmadrops.dk/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.
Parts of the site are closed to 4 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
2 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (5,119 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pharmadrops.dk/llms.txt (8 KiB, 34 links), a plain-text guide to the site for AI tools.
Other pages
7 pages point its canonical at the homepage
https://pharmadrops.dk/shop, https://pharmadrops.dk/cases, https://pharmadrops.dk/cbd-olie-soevn, https://pharmadrops.dk/cbd-olie-smerter, https://pharmadrops.dk/cbd-olie-stress and https://pharmadrops.dk/cbd-olie-angst and 1 other declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
10 pages share 2 titles
/, https://pharmadrops.dk/shop, https://pharmadrops.dk/cases, https://pharmadrops.dk/cbd-olie-soevn, https://pharmadrops.dk/cbd-olie-smerter and https://pharmadrops.dk/cbd-olie-stress and 2 others all use the title “CBD Olie i Høj Kvalitet – Dansk Webshop | Pharmadrops”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages share a meta description
https://pharmadrops.dk/shop, https://pharmadrops.dk/om-os, https://pharmadrops.dk/cases, https://pharmadrops.dk/produkt/10, https://pharmadrops.dk/produkt/20 and https://pharmadrops.dk/produkt/30 and 8 others use the same meta description. A description written for each page earns more clicks.
4 pages without an H1
https://pharmadrops.dk/olie, https://pharmadrops.dk/produkt/10, https://pharmadrops.dk/produkt/20 and https://pharmadrops.dk/produkt/30 have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://pharmadrops.dk/om-os, https://pharmadrops.dk/produkt/10, https://pharmadrops.dk/produkt/20, https://pharmadrops.dk/produkt/30, https://pharmadrops.dk/cbd-test and https://pharmadrops.dk/cbd-hudpleje 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 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 a meta description
All 15 pages that loaded have a meta description.
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 “X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>.”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
16 of 17 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.
Only about 226 words
The homepage has only about 226 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Shop”.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, 16 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Microsoft Clarity (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
5 other companies contacted
Loading the homepage contacts 5 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 pharmadrops.dk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on pharmadrops.dk, including 16 speed issues, 1 SEO issue and 2 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.