Website review, no card needed
alexandria.fi website review
Visit site (opens in a new tab)Reviewed 19 October 202616 issues · 76 checks
This review found 16 issues worth fixing on alexandria.fi, 5 of them high impact, across 76 checks. The most urgent: 7 tap targets too small. 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.3 s |
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 143 ms |
| May 2, 2026 | 142 ms |
| May 9, 2026 | 138 ms |
| May 16, 2026 | 139 ms |
| May 23, 2026 | 140 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 141 ms |
| Jun 27, 2026 | 143 ms |
| Jul 4, 2026 | 142 ms |
| Jul 11, 2026 | 142 ms |
| Jul 18, 2026 | 141 ms |
| Jul 25, 2026 | 140 ms |
| Aug 1, 2026 | 140 ms |
| Aug 8, 2026 | 140 ms |
| Aug 15, 2026 | 142 ms |
| Aug 22, 2026 | 142 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 135 ms |
| Sep 12, 2026 | 132 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 126 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 127 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 87
87/100Your mobile performance score is 87 (desktop: 79). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.1 MB and 830 ms of main-thread time.
Reduce unused JavaScript
472 KiBAbout 472 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
467 KiB15 files are served with short cache lifetimes, so returning visitors download them again (467 KiB).
Google Tag Manager adds 346 ms
346 msGoogle Tag Manager costs a phone 346 ms of main-thread work and 508 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 172 KiB7 images could be 172 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 167 ms. During a long task the page ignores taps.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 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.
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: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 18.8 s
18.8 sThe page becomes fully interactive after 18.8 s. Good is under 3.8 s.
Total Blocking Time: 426 ms
426 msScripts block taps and scrolling for 426 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 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: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 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: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 634 ms
634 msReal visitors wait 634 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 143 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.4 s
2.4 sYour largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Kun varallisuutta on kertynyt, sen hoitaminen vaatii kokona…”.
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.
Speed Index: 2.4 s
2.4 sVisually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 105 requests
2.2 MBYour homepage downloads 2.2 MB in 105 requests on a phone: scripts 1.4 MB (36), images 336 KiB (23) and other files 309 KiB (40). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.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
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
2 checks passed
Every image has alt text
All 48 images in the HTML carry an alt attribute.
47 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: 47 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
86 internal links, 7 external
The homepage links to 86 pages on alexandria.fi and 7 external pages.
8 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Alexandria tarjoaa asiantuntevaa varainhoitoa ja sijoitusratkaisuita. Asiakastyytyväisyytemme on 9,4 – tavoitteellista …”.
One H1 headline
Your main headline reads: “Varainhoito Alexandriassa”.
Title: 62 characters
Your title is a healthy 62 characters: “Varainhoito, rahastot ja sijoitukset | Alexandria | Alexandria”.
Canonical URL set
The canonical URL is https://www.alexandria.fi/.
Structured data in place
Structured data found: Organization and WebSite.
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.alexandria.fi/sitemap-index.xml.
AI search readiness
No llms.txt
There is no https://www.alexandria.fi/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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (516 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.alexandria.fi/sijoita-verkossa has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 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.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187242375&Ver=2&mid=354c1528-75b6-41e5-8395-883f501c7667&bo=6&sid=cfaf7cd0cb5111f1b2a9c1abe35df66c&vid=cfaf92d0cb5111f1b407df8fa9603b62&vids=1&msclkid=N&pi=918639831&l.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
37 of 39 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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 12 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 509 words of copy
The homepage carries about 509 words of visible text.
3 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, HubSpot and LinkedIn Insight and 2 mores (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
29 other companies contacted
Loading the homepage contacts 29 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 alexandria.fi, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Gatsby
- Analytics
- Google Tag Manager
- Hosting
- Netlify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 16 issues on alexandria.fi, including 8 speed 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.