Website review, no card needed

forenom.com logo

forenom.com website review

Visit site (opens in a new tab)Reviewed 31 October 202649 issues · 89 checks

This review found 49 issues worth fixing on forenom.com, 21 of them high impact, across 89 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
3.9 s3.3 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.6 s
May 16, 20263.6 s
May 23, 20263.5 s
May 30, 20263.4 s
Jun 6, 20263.5 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.7 s
Jul 11, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.5 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.6 s
Oct 3, 20263.7 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
256 ms232 msMay 9Oct 24247 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026244 ms
May 16, 2026249 ms
May 23, 2026253 ms
May 30, 2026252 ms
Jun 6, 2026252 ms
Jun 13, 2026249 ms
Jun 20, 2026243 ms
Jun 27, 2026242 ms
Jul 4, 2026244 ms
Jul 11, 2026243 ms
Jul 18, 2026245 ms
Jul 25, 2026245 ms
Aug 1, 2026245 ms
Aug 8, 2026245 ms
Aug 15, 2026243 ms
Aug 22, 2026238 ms
Aug 29, 2026237 ms
Sep 5, 2026235 ms
Sep 12, 2026239 ms
Sep 19, 2026247 ms
Sep 26, 2026248 ms
Oct 3, 2026250 ms
Oct 10, 2026252 ms
Oct 17, 2026247 ms
Oct 24, 2026247 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 forenom.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. forenom.com at 0.5 s0.5 s
  2. forenom.com at 0.9 s0.9 s
  3. forenom.com at 1.4 s1.4 s
  4. forenom.com at 1.9 s1.9 s
  5. forenom.com at 2.3 s2.3 s
  6. forenom.com at 2.8 s2.8 s
  7. forenom.com at 3.2 s3.2 s
  8. forenom.com at 3.7 s3.7 s

Speed

14 to fix6
  • Reduce unused JavaScript

    4.4 s · 866 KiB

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

  • Render-blocking requests

    5.3 s

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

  • Use efficient cache lifetimes

    3.0 s · 714 KiB

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

  • Mobile performance score: 6

    6/100

    Your mobile performance score is 6. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    1.2 MB

    12 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Sentry, Google Tag Manager and Google Maps and others), adding 1.3 MB and 1.1 s of main-thread time.

  • Legacy JavaScript

    550 ms · 58 KiB

    Polyfills for old browsers add 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.

  • Main-thread work: 3.6 s

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

  • Sentry adds 331 ms

    331 ms

    Sentry costs a phone 331 ms of main-thread work and 33 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.

  • 15 long tasks on the main thread

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

  • Google Tag Manager adds 259 ms

    259 ms

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

  • 2,348 HTML elements

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

  • Google Maps adds 188 ms

    188 ms

    Google Maps costs a phone 188 ms of main-thread work and 405 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.

  • awswaf.com adds 123 ms

    123 ms

    awswaf.com costs a phone 123 ms of main-thread work and 307 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.

  • Reduce unused CSS

    270 ms · 78 KiB

    About 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 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.

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

12 to fix33
  • 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 CLS: 1.00

    1.00

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

  • Largest Contentful Paint: 18.0 s

    18.0 s

    Your largest element takes 18.0 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 personalise content and ads, to provide s…”.

  • Cumulative Layout Shift: 1

    1

    The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 6.6 s

    6.6 s

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

  • Time to Interactive: 18.1 s

    18.1 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 896 ms

    896 ms

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

  • 12 images without width and height

    12 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

1 checks passed
  • Real-user INP: 176 ms

    176 ms

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

Images and page weight

2 to fix63
  • Page weight: 4.2 MB in 140 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 140 requests on a phone: scripts 2.3 MB (75), images 1.5 MB (22) and fonts 144 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

    6 images further down the page (377 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 7 images in older formats

    7 images (468 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 1.2 g of CO₂ per visit

    1.18 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8488
  • Images must have alternative text (9 elements)

    Images must have alternative text: 9 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Heading levels should only increase by one (2 elements)

    Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

  • 6 links without text

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

5 to fixGoogle 7777
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Furnished apartments, hostels and aparthotels - Forenom accommodation”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 72 internal links, 8 external

    The homepage links to 72 pages on forenom.com and 8 external pages.

5 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “We provide accommodation from single hostel rooms and apartment hotels to entire furnished apartments. Book your stay h…”.

  • Canonical URL set

    The canonical URL is https://www.forenom.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.forenom.com/sitemap_index.xml.

AI search readiness

2 to fix75
  • Some text only appears after JavaScript runs

    39%

    The HTML your server sends has 195 of the 496 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • 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.forenom.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.

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

Other pages

3 to fix83
  • 2 pages share a title

    / and https://www.forenom.com/de all use the title “Furnished apartments, hostels and aparthotels - Forenom accommodation”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.forenom.com/da has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.forenom.com/fi, https://www.forenom.com/sv, https://www.forenom.com/nb, https://www.forenom.com/da, https://www.forenom.com/de and https://www.forenom.com/subscribe-to-our-newsletter have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.forenom.com/fi, https://www.forenom.com/de and https://www.forenom.com/ru 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.

  • 1 page slow to respond

    https://www.forenom.com/flexible-housing-for-grid-and-electrification-projects took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

Google 100100
  • 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

    19 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • About 496 words of copy

    The homepage carries about 496 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book online”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies (measured from a US location before any click).

  • 19 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
CloudFront

Company

Founded
2001
Headquarters
Helsinki

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on forenom.com, including 26 speed issues, 5 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