Website review, no card needed

fernish.com logo

fernish.com website review

Visit site (opens in a new tab)Reviewed 5 November 202628 issues · 90 checks

This review found 28 issues worth fixing on fernish.com, 4 of them high impact, across 90 checks. The most urgent: 2 linked pages are broken. 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.3 s1.0 sMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.1 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
108 ms74 msMay 16Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202678 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202688 ms
Jun 13, 202688 ms
Jun 20, 202687 ms
Jun 27, 202697 ms
Jul 4, 202687 ms
Jul 11, 202688 ms
Jul 18, 202693 ms
Jul 25, 202682 ms
Aug 1, 202686 ms
Aug 8, 202686 ms
Aug 15, 202687 ms
Aug 22, 202694 ms
Aug 29, 202698 ms
Sep 5, 202692 ms
Sep 12, 202686 ms
Sep 19, 202694 ms
Sep 26, 202695 ms
Oct 3, 2026102 ms
Oct 10, 2026104 ms
Oct 17, 2026101 ms
Oct 24, 202699 ms
Oct 31, 202696 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

Live view · interaction off

Speed

3 to fix76
  • Mobile performance score: 76

    76/100

    Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    670 ms · 146 KiB

    About 146 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 670 ms faster on a phone.

  • Render-blocking requests

    500 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

  • Improve image delivery

    227 KiB

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

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    90 ms · 11 KiB

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

  • 1 third-party service on the page

    1 third-party service load with your homepage (browser-intake-datadoghq.com), adding 2 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 311 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 5.3 s

    5.3 s

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

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

    +24%

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Time to Interactive: 5.5 s

    5.5 s

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

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

    1.2 s

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

  • Real-user INP: 95 ms

    95 ms

    Real visitors wait 95 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 558 ms

    558 ms

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

  • Speed Index: 2.9 s

    2.9 s

    Visually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 77 ms

    77 ms

    Scripts block the page for only 77 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.35 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.35 g of CO₂e: 42.5 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.2 MB in 52 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 52 requests on a phone: scripts 549 KiB (21), images 387 KiB (10) and fonts 266 KiB (6). 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

1 to fixGoogle 10099
  • Alternative text of images should not be repeated as text (8 elements)

    Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 10063
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Fernish: Furniture rental for an easier and more sustainable home.”.

  • No structured data

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

  • Meta description is short (67 characters)

    Your meta description is only 67 characters: “Rent, rent-to-own, or buy furniture and décor from brands you love.”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Furniture, made light.” and “Furniture, made light.”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

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

  • No X (Twitter) card tag

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

  • 15 internal links, 0 external

    The homepage links to 15 pages on fernish.com and 0 external pages.

1 checks passed
  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix83
  • 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 /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 fix69
  • 2 linked pages are broken

    Your homepage links to /n/room_types/living-room and /n/room_types/bedroom, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 7 pages share a meta description

    /n/room_types, /n/room_types/dining-room, /n/room_types/offices, /n/item_types/bedframes/items, /n/item_types/dining-tables/items and /n/item_types/sofas-sectionals/items and 1 other use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    /n/room_types/dining-room, /n/room_types/offices, /n/item_types/bedframes/items, /n/item_types/dining-tables/items, /n/item_types/sofas-sectionals/items and /n/item_types/desks/items have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    /n/room_types, /n/room_types/dining-room, /n/room_types/offices, /n/item_types/bedframes/items, /n/item_types/dining-tables/items and /n/item_types/sofas-sectionals/items and 1 other 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.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • 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 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 3 small tap targets

    3 of 13 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.

Security and trust

3 to fix71
  • 2 broken links to your own pages

    2 links from your homepage to your own site are broken, for example https://fernish.com/n/room_types/living-room (404).

  • No HSTS header

    No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

4 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (fernish.com).

  • Valid certificate (177 days left)

    The certificate from Amazon · Amazon RSA 2048 M04 verifies for fernish.com and is valid for another 177 days.

  • http:// redirects to https

    http://fernish.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

Domain and trust

  • DNSSEC is off

    fernish.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

3 checks passed
  • Domain is 25 years old

    25 years

    fernish.com was registered in Aug 2001 through Amazon Registrar, Inc.. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only amazonaws.com, amazontrust.com, awstrust.com and amazon.com to issue certificates for fernish.com, so a mis-issued certificate from anyone else is refused.

  • Registered until Aug 2027

    fernish.com is registered until Aug 2027.

Content and conversion

4 to fix67
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 35 words

    The homepage has only about 35 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start shopping”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Start shopping”.

Email authentication

1 to fix70
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be fernish.com is still delivered. Reports are on, so moving to quarantine is the next step.

  • Email authentication score: 70/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

2 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:mailgun.org ~all”.

  • DKIM signing found

    A DKIM key is published (selector “google”, “k1” and “s1”), so receivers can verify mail really came from you.

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
CloudFront

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on fernish.com, including 7 speed issues, 7 SEO 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

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