Website review, no card needed
academedia.se website review
Visit site (opens in a new tab)Reviewed 20 October 202629 issues · 72 checks
This review found 29 issues worth fixing on academedia.se, 12 of them high impact, across 72 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 2, 2026 | 4.3 s |
| May 9, 2026 | 4.2 s |
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 5.3 s |
| Jun 20, 2026 | 5.8 s |
| Jun 27, 2026 | 6.0 s |
| Jul 4, 2026 | 6.2 s |
| Jul 11, 2026 | 6.3 s |
| Jul 18, 2026 | 6.3 s |
| Jul 25, 2026 | 6.4 s |
| Aug 1, 2026 | 6.4 s |
| Aug 8, 2026 | 6.3 s |
| Aug 15, 2026 | 6.2 s |
| Aug 22, 2026 | 6.0 s |
| Aug 29, 2026 | 6.1 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.1 s |
| Sep 19, 2026 | 5.9 s |
| Sep 26, 2026 | 5.6 s |
| Oct 3, 2026 | 5.5 s |
| Oct 10, 2026 | 5.4 s |
| Oct 17, 2026 | 5.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 158 ms |
| May 9, 2026 | 155 ms |
| May 16, 2026 | 157 ms |
| May 23, 2026 | 155 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 156 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 161 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 142 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 138 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 153 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
Reduce unused JavaScript
2.7 s · 501 KiBAbout 501 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 734 KiB11 files are served with short cache lifetimes, so returning visitors download them again (734 KiB).
Render-blocking requests
1.0 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 65
65/100Your mobile performance score is 65 (desktop: 52). Pages that score under 90 lose visitors before the first paint.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 253 ms. During a long task the page ignores taps.
Improve image delivery
150 ms · 247 KiB6 images could be 247 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.
Legacy JavaScript
150 ms · 64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and cookietractor.com), adding 187 KiB and 78 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.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 333 ms of it running JavaScript. That is comfortably low.
Server response: 120 ms
120 msYour server sent the HTML in 120 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 FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.7 s
2.7 sReal visitors wait 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.3 s
10.3 sThe page becomes fully interactive after 10.3 s. Good is under 3.8 s.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 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 4.3 s to 5.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
131 images without width and height
131 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 211 ms
211 msScripts block taps and scrolling for 211 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 158 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 162 ms
162 msReal visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 71 requests
2.1 MBYour homepage downloads 2.1 MB in 71 requests on a phone: images 986 KiB (52), scripts 872 KiB (13) and fonts 208 KiB (3). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (158 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.
About 0.6 g of CO₂ per visit
0.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 69.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
1 checks passed
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 0 failed. 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 1 problem
Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: url points at a different host (https://wp.academedia.se/)”.
No XML sitemap
No XML sitemap at https://academedia.se/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 set, so this is minor.
18 internal links, 5 external
The homepage links to 18 pages on academedia.se and 5 external pages.
5 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “AcadeMedia består av människor som brinner för att skapa ett bättre och mer hållbart samhälle, med utbildning och läran…”.
Title: 37 characters
Your title is a healthy 37 characters: “Utbildning som förändrar - AcadeMedia”.
Canonical URL set
The canonical URL is https://academedia.se/.
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.
AI search readiness
Some text only appears after JavaScript runs
34%The HTML your server sends has 82 of the 240 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://academedia.se/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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
2 pages without a meta description
https://academedia.se/om-oss/investerare and https://academedia.se/tillganglighetsredogorelse have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://academedia.se/vara-utbildningar, https://academedia.se/om-oss, https://academedia.se/nyhetsrum, https://academedia.se/jobba-hos-oss, https://academedia.se/en and https://academedia.se/om-oss/investerare and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://academedia.se/vara-utbildningar, https://academedia.se/om-oss, https://academedia.se/nyhetsrum, https://academedia.se/kontakt, https://academedia.se/jobba-hos-oss and https://academedia.se/en 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.
5 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.
Titles are unique
Every page we checked has its own title.
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
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
13 of 16 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.
Only about 240 words
The homepage has only about 240 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.
2 checks passed
Analytics in place
Analytics detected: Google Analytics and Matomo.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
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.
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 academedia.se, 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
- Analytics
- Google Analytics | Matomo
Company
- Founded
- 1996
- Headquarters
- Stockholm
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on academedia.se, including 16 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.