Website review, no card needed

fastnedcharging.com logo

fastnedcharging.com website review

Visit site (opens in a new tab)Reviewed 2 November 202635 issues · 79 checks

This review found 35 issues worth fixing on fastnedcharging.com, 8 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.

  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
2.1 s1.8 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
136 ms108 msMay 16Oct 31129 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026111 ms
May 23, 2026111 ms
May 30, 2026112 ms
Jun 6, 2026114 ms
Jun 13, 2026117 ms
Jun 20, 2026118 ms
Jun 27, 2026119 ms
Jul 4, 2026119 ms
Jul 11, 2026120 ms
Jul 18, 2026121 ms
Jul 25, 2026121 ms
Aug 1, 2026122 ms
Aug 8, 2026121 ms
Aug 15, 2026124 ms
Aug 22, 2026126 ms
Aug 29, 2026128 ms
Sep 5, 2026129 ms
Sep 12, 2026130 ms
Sep 19, 2026131 ms
Sep 26, 2026131 ms
Oct 3, 2026133 ms
Oct 10, 2026131 ms
Oct 17, 2026129 ms
Oct 24, 2026129 ms
Oct 31, 2026129 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 fastnedcharging.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fastnedcharging.com at 0.5 s0.5 s
  2. fastnedcharging.com at 1.0 s1.0 s
  3. fastnedcharging.com at 1.6 s1.6 s
  4. fastnedcharging.com at 2.1 s2.1 s
  5. fastnedcharging.com at 2.6 s2.6 s
  6. fastnedcharging.com at 3.1 s3.1 s
  7. fastnedcharging.com at 3.6 s3.6 s
  8. fastnedcharging.com at 4.1 s4.1 s

Speed

10 to fix55
  • Reduce unused JavaScript

    2.9 s · 613 KiB

    About 613 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Use efficient cache lifetimes

    1.5 s · 332 KiB

    27 files are served with short cache lifetimes, so returning visitors download them again (332 KiB).

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. 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, viral-loops.com and Cookiebot and others), adding 1.0 MB and 516 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 82 KiB

    About 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 341 ms

    341 ms

    Google Tag Manager costs a phone 341 ms of main-thread work and 583 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.

  • 8 long tasks on the main thread

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

  • Main-thread work: 2.6 s

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

  • 2,128 HTML elements

    The page has 2,128 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    150 ms · 12 KiB

    1 image could be 12 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.

  • 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: 94 ms

    94 ms

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

Core Web Vitals

7 to fix67
  • 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: 11.1 s

    11.1 s

    Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to ensure our website functions properly, pe…”.

  • Time to Interactive: 11.3 s

    11.3 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • Total Blocking Time: 504 ms

    504 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user INP: 133 ms

    133 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 616 ms

    616 ms

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

  • Cumulative Layout Shift: 0.015

    0.015

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

Images and page weight

100
  • 2 images in older formats

    2 images (239 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.

  • 1 image below the first screen load straight away

    1 image further down the page (129 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.4 g of CO₂ per visit

    0.45 g

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

2 checks passed
  • Page weight: 1.6 MB in 46 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 46 requests on a phone: scripts 1.2 MB (28), images 240 KiB (3) and stylesheets 94 KiB (3). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8894
  • 13 images without alt text

    13 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 27 links without text

    27 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 7785
  • Title is long (90 characters)

    Your title is 90 characters, so Google will cut it off around 60: “Fastned | Ultrafast charging stations for electric cars, vans, motors and trucks | Fastned”.

  • Structured data has 2 problems

    Structured data found (Organization) but with 2 problems, for example “Organization: url is not an absolute URL ("https://www.fastnedcharging.com/en")”.

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 94 internal links, 11 external

    The homepage links to 94 pages on fastnedcharging.com and 11 external pages.

6 checks passed
  • Meta description: 117 characters

    Your meta description is 117 characters: “Charge up to 333 km in 10 minutes at 350+ locations across Europe. Reliable fast charging with chargers up to 400 kW.”.

  • One H1 headline

    Your main headline reads: “Fast charging for people”.

  • Canonical URL set

    The canonical URL is https://www.fastnedcharging.com/en.

  • 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.fastnedcharging.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.fastnedcharging.com/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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (635 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.fastnedcharging.com/en/for-business/investor-relations, https://www.fastnedcharging.com/en/our-station-concept and https://www.fastnedcharging.com/en/about/sustainability-and-community have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://www.fastnedcharging.com/en/for-business/investor-relations, https://www.fastnedcharging.com/en/locations, https://www.fastnedcharging.com/en/for-business/location-partners, https://www.fastnedcharging.com/en/charging/how-to-charge, https://www.fastnedcharging.com/en/charging/tariffs and https://www.fastnedcharging.com/en/brands-overview and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 8885
  • 4 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://cdn.taboola.com/libtrc/unip/1985304/tfa.js' violates the following Content Security Policy …”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 508 words of copy

    The homepage carries about 508 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Learn more”, “Learn more at bcorp.com” and “Subscribe”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 fastnedcharging.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
40 open roles
Teams
Network Development (16), Finance & Funding (4), Commercial Team (3), Construction Management (3)
Job board
recruitee

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on fastnedcharging.com, including 17 speed issues, 4 SEO 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