Website review, no card needed

fortnox.se logo

fortnox.se website review

Visit site (opens in a new tab)Reviewed 26 October 202620 issues · 78 checks

This review found 20 issues worth fixing on fortnox.se, 5 of them high impact, across 78 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.5 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.7 s
May 23, 20261.8 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
252 ms198 msMay 9Oct 24204 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026246 ms
May 16, 2026238 ms
May 23, 2026237 ms
May 30, 2026239 ms
Jun 6, 2026240 ms
Jun 13, 2026241 ms
Jun 20, 2026238 ms
Jun 27, 2026239 ms
Jul 4, 2026239 ms
Jul 11, 2026241 ms
Jul 18, 2026240 ms
Jul 25, 2026239 ms
Aug 1, 2026238 ms
Aug 8, 2026237 ms
Aug 15, 2026238 ms
Aug 22, 2026237 ms
Aug 29, 2026239 ms
Sep 5, 2026238 ms
Sep 12, 2026230 ms
Sep 19, 2026220 ms
Sep 26, 2026212 ms
Oct 3, 2026204 ms
Oct 10, 2026204 ms
Oct 17, 2026205 ms
Oct 24, 2026204 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

Full-page screenshot of fortnox.se (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fortnox.se at 0.6 s0.6 s
  2. fortnox.se at 1.2 s1.2 s
  3. fortnox.se at 1.8 s1.8 s
  4. fortnox.se at 2.3 s2.3 s
  5. fortnox.se at 2.9 s2.9 s
  6. fortnox.se at 3.5 s3.5 s
  7. fortnox.se at 4.1 s4.1 s
  8. fortnox.se at 4.7 s4.7 s

Speed

6 to fix66
  • Render-blocking requests

    1.6 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    517 KiB

    About 517 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    300 ms · 73 KiB

    About 73 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.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 327 ms. During a long task the page ignores taps.

  • Main-thread work: 3.2 s

    A phone's processor spends 3.2 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3 third-party services on the page

    3 third-party services load with your homepage (piwik.pro, Google Tag Manager and storyblok.com), adding 625 KiB and 305 ms of main-thread time.

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 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.

  • Improve image delivery

    4 KiB

    1 image could be 4 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    2 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (2 KiB).

1 checks passed
  • Server response: 323 ms

    323 ms

    Your server sent the HTML in 323 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Time to Interactive: 11.9 s

    11.9 s

    The page becomes fully interactive after 11.9 s. Good is under 3.8 s.

  • Speed Index: 7.1 s

    7.1 s

    Visually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 764 ms

    764 ms

    Scripts block taps and scrolling for 764 ms in total while the page loads. Good is under 200 ms.

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

9 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.1 s

    1.1 s

    Real visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 177 ms

    177 ms

    Real visitors wait 177 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 646 ms

    646 ms

    Real visitors wait 646 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 15% faster for real visitors

    -15%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 246 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.019

    0.019

    The layout barely moves while loading (CLS 0.019, good is under 0.1).

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.48 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 58.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed
  • Page weight: 1.7 MB in 43 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 43 requests on a phone: scripts 1.1 MB (16), images 267 KiB (9) and stylesheets 112 KiB (10). That is a lean page.

  • 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

3 to fixGoogle 9797
  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 17 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. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 92100
  • 103 internal links, 23 external

    The homepage links to 103 pages on fortnox.se and 23 external pages.

8 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Fortnox företagsplattform effektiviserar dina administrativa sysslor, hjälper dig hitta nya kunder, få enklare betalt e…”.

  • One H1 headline

    Your main headline reads: “Allt för att starta, driva och växa”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Sverigeledande på webbaserad bokföring och fakturering | Fortnox”.

  • Canonical URL set

    The canonical URL is https://www.fortnox.se/home.

  • Structured data in place

    Structured data found: Corporation, ImageObject 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.fortnox.se/sitemap.xml.

AI search readiness

100
4 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 (892 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.fortnox.se/llms.txt (5 KiB, 4 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 2 linked pages hidden from search

    https://www.fortnox.se/starta-foretag and https://www.fortnox.se/kontakt/foretagare are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 59 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 10 small tap targets

    10 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • 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: 3 testimonial or review blocks. 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 576 words of copy

    The homepage carries about 576 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Boka demo”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 fortnox.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
Next.js
Analytics
Google Analytics

Company

Founded
2001

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on fortnox.se, including 11 speed issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25