Website review, no card needed

fama.es logo

fama.es website review

Visit site (opens in a new tab)Reviewed 23 October 202637 issues · 76 checks

This review found 37 issues worth fixing on fama.es, 18 of them high impact, across 76 checks. The most urgent: improve image delivery. 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
8.1 s6.9 sMay 2Oct 177.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20268.0 s
May 9, 20267.9 s
May 16, 20267.8 s
May 23, 20267.7 s
May 30, 20267.7 s
Jun 6, 20267.7 s
Jun 13, 20267.7 s
Jun 20, 20267.8 s
Jun 27, 20267.8 s
Jul 4, 20267.8 s
Jul 11, 20267.7 s
Jul 18, 20267.4 s
Jul 25, 20267.3 s
Aug 1, 20267.2 s
Aug 8, 20267.2 s
Aug 15, 20267.2 s
Aug 22, 20267.3 s
Aug 29, 20267.3 s
Sep 5, 20267.2 s
Sep 12, 20267.2 s
Sep 19, 20267.1 s
Sep 26, 20267.2 s
Oct 3, 20267.1 s
Oct 10, 20267.1 s
Oct 17, 20267.0 s
Real-visitor tap response (INP)75th percentile, phones
149 ms125 msMay 2Oct 17128 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026146 ms
May 9, 2026141 ms
May 16, 2026137 ms
May 23, 2026134 ms
May 30, 2026135 ms
Jun 6, 2026135 ms
Jun 13, 2026132 ms
Jun 20, 2026130 ms
Jun 27, 2026130 ms
Jul 4, 2026135 ms
Jul 11, 2026138 ms
Jul 18, 2026138 ms
Jul 25, 2026138 ms
Aug 1, 2026136 ms
Aug 8, 2026137 ms
Aug 15, 2026137 ms
Aug 22, 2026138 ms
Aug 29, 2026137 ms
Sep 5, 2026136 ms
Sep 12, 2026136 ms
Sep 19, 2026131 ms
Sep 26, 2026131 ms
Oct 3, 2026129 ms
Oct 10, 2026128 ms
Oct 17, 2026128 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 fama.es (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fama.es at 1.0 s1.0 s
  2. fama.es at 1.9 s1.9 s
  3. fama.es at 2.9 s2.9 s
  4. fama.es at 3.8 s3.8 s
  5. fama.es at 4.8 s4.8 s
  6. fama.es at 5.7 s5.7 s
  7. fama.es at 6.7 s6.7 s
  8. fama.es at 7.6 s7.6 s

Speed

9 to fix45
  • Improve image delivery

    1.2 s · 2.0 MB

    12 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Reduce unused JavaScript

    1.2 s · 689 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 45

    45/100

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

  • Reduce unused CSS

    900 ms · 146 KiB

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

  • Font display

    800 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).

  • Google Tag Manager adds 314 ms

    314 ms

    Google Tag Manager costs a phone 314 ms of main-thread work and 357 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.8 s

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

  • 2,297 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Pinterest and Hotjar and others), adding 817 KiB and 480 ms of main-thread time.

  • 9 long tasks on the main thread

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

  • Duplicated JavaScript

    130 KiB

    130 KiB JavaScript is shipped twice across bundles.

  • Use efficient cache lifetimes

    20 KiB

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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: 109 ms

    109 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.3 s

    4.3 s

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

  • Real-user FCP: 4.0 s

    4.0 s

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

  • Real-user TTFB: 3.0 s

    3.0 s

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

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 22.5 s

    22.5 s

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

  • Largest Contentful Paint: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Modular recliner with Coud Seating”. Most of its time is element render delay (3.4 s).

  • Cumulative Layout Shift: 0.247

    0.247

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Total Blocking Time: 225 ms

    225 ms

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

4 checks passed
  • Real-user INP: 134 ms

    134 ms

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

  • Real-user CLS: 0.01

    0.01

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

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

    -11%

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

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

    -11%

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

Images and page weight

4 to fix28
  • Page weight: 6.0 MB in 114 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 114 requests on a phone: images 3.6 MB (69), scripts 1.1 MB (19) and fonts 773 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    1.1 MB

    7 images are downloaded at several times the size a phone draws them, for example home-felicidad.webp at 1,600 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

  • 7 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (279 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.7 g of CO₂ per visit

    1.71 g

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

Accessibility

4 to fixGoogle 9188
  • 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.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 24 images without alt text

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

  • 1 form field without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 26 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 28 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 2 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 8385
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 9 H1 headlines

    There are 9 <h1> headlines (“CONTEST”, “Fama Non-stop” and “News”). One clear main headline is easier for people and search engines.

  • No XML sitemap

    No XML sitemap at https://famasofas.com/sitemap.xml, so Google discovers your pages only by following links.

  • 2 links with vague text

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

  • 228 internal links, 40 external

    The homepage links to 228 pages on fama.es and 40 external pages.

5 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Fama is the Spanish brand of sofas especially designed and produced to enjoy at home. This company is committed to soci…”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Fama Sofas | Sofas to enjoy at home | Fama Sofas”.

  • Canonical URL set

    The canonical URL is https://famasofas.com/inicio-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.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://famasofas.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 (1,557 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://famasofas.com/inicio-en.

  • 55 small tap targets

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

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

2 to fix86
  • Thin social proof

    Social proof on the homepage: 19 customer or partner logos. 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.

  • About 958 words of copy

    The homepage carries about 958 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact us”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Microsoft Clarity and 1 more (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.

  • 10 cookies set on arrival

    10

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

  • 18 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on fama.es, including 19 speed issues, 4 SEO issues and 2 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