Website review, no card needed

farreys.com logo

farreys.com website review

Visit site (opens in a new tab)Reviewed 20 October 202651 issues · 93 checks

This review found 51 issues worth fixing on farreys.com, 20 of them high impact, across 93 checks. The most urgent: use efficient cache lifetimes. 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
16.9 s7.6 sMay 16Oct 178.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 202612.2 s
May 23, 202613.3 s
May 30, 202613.8 s
Jun 6, 202614.3 s
Jun 13, 202614.4 s
Jun 20, 202614.5 s
Jun 27, 202614.9 s
Jul 4, 202615.1 s
Jul 11, 202615.3 s
Jul 18, 202615.4 s
Jul 25, 202615.6 s
Aug 1, 202615.7 s
Aug 8, 202615.8 s
Aug 15, 202615.1 s
Aug 22, 202614.2 s
Aug 29, 202612.8 s
Sep 5, 202612.0 s
Sep 12, 202611.6 s
Sep 19, 202611.2 s
Sep 26, 202610.8 s
Oct 3, 202610.1 s
Oct 10, 20269.5 s
Oct 17, 20268.7 s
Real-visitor tap response (INP)75th percentile, phones
255 ms118 msMay 23Oct 17239 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026172 ms
May 30, 2026144 ms
Jun 6, 2026144 ms
Jun 13, 2026134 ms
Jun 20, 2026135 ms
Jun 27, 2026161 ms
Jul 4, 2026147 ms
Jul 11, 2026170 ms
Jul 18, 2026177 ms
Jul 25, 2026163 ms
Aug 1, 2026184 ms
Aug 8, 2026185 ms
Aug 15, 2026173 ms
Aug 22, 2026157 ms
Aug 29, 2026140 ms
Sep 5, 2026141 ms
Sep 12, 2026158 ms
Sep 19, 2026182 ms
Sep 26, 2026201 ms
Oct 3, 2026209 ms
Oct 10, 2026226 ms
Oct 17, 2026239 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 farreys.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. farreys.com at 0.8 s0.8 s
  2. farreys.com at 1.6 s1.6 s
  3. farreys.com at 2.4 s2.4 s
  4. farreys.com at 3.2 s3.2 s
  5. farreys.com at 4.0 s4.0 s
  6. farreys.com at 4.8 s4.8 s
  7. farreys.com at 5.6 s5.6 s
  8. farreys.com at 6.4 s6.4 s

Speed

10 to fix55
  • Use efficient cache lifetimes

    3.1 s · 4.2 MB

    73 files are served with short cache lifetimes, so returning visitors download them again (4.2 MB).

  • Reduce unused JavaScript

    1.9 s · 595 KiB

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

  • Render-blocking requests

    1.9 s

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

  • Improve image delivery

    150 ms · 2.5 MB

    30 images could be 2.5 MB 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Adobe Tag Manager and others), adding 1.1 MB and 924 ms of main-thread time.

  • Mobile performance score: 55

    55/100

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

  • Google Tag Manager adds 552 ms

    552 ms

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

    530 ms · 92 KiB

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

  • Main-thread work: 2.9 s

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

  • 9 long tasks on the main thread

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

  • Font display

    200 ms

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

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • Minify CSS

    10 KiB

    10 KiB could be saved by minifying CSS.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 33 ms

    33 ms

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

Core Web Vitals

13 to fix0
  • 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: 8.7 s

    8.7 s

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

  • Real-user CLS: 0.28

    0.28

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

  • Real-user FCP: 7.1 s

    7.1 s

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

  • Real-user TTFB: 6.4 s

    6.4 s

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

  • Largest Contentful Paint: 17.1 s

    17.1 s

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

  • Speed Index: 15.3 s

    15.3 s

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

  • Time to Interactive: 23.8 s

    23.8 s

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

  • Real-user INP: 239 ms

    239 ms

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

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

    +47%

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Total Blocking Time: 299 ms

    299 ms

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

  • 5 images without width and height

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

2 checks passed
  • Largest content (LCP) got 29% faster for real visitors

    -29%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix33
  • Page weight: 5.1 MB in 110 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 110 requests on a phone: images 3.4 MB (42), scripts 1.4 MB (33) and fonts 127 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 21 images far larger than shown

    1.9 MB

    21 images are downloaded at several times the size a phone draws them, for example BALDWIN_.jpg at 768 px wide, shown at 108 px. Resized copies would save about 1.9 MB.

  • 30 images in older formats

    30 images (3.4 MB) 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.

  • 28 images below the first screen load straight away

    28 images further down the page (3.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.45 g

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

Accessibility

10 to fixGoogle 5982
  • Orphan list items

    Some list items are not inside a list.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

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

  • 8 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 25 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 passed and 10 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 9266
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is long (156 characters)

    Your title is 156 characters, so Google will cut it off around 60: “Farrey's Lighting, Bath, and Decorative Hardware – Farrey’s is South Florida’s leading li…”.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 42 internal links, 13 external

    The homepage links to 42 pages on farreys.com and 13 external pages.

3 checks passed
  • Canonical URL set

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

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

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://www.farreys.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,011 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.farreys.com/shop-all-lighting, https://www.farreys.com/shop-all-bath, https://www.farreys.com/shop-all-kitchen, https://www.farreys.com/shop-all-decorative-hardware, https://www.farreys.com/shop-all-brands and https://www.farreys.com/shop-our-showroom-display-products and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.farreys.com/contact-us, https://www.farreys.com/visiting-farreys, https://www.farreys.com/jewelry-for-the-home, https://www.farreys.com/trade-program and https://www.farreys.com/bienvenido-a-farreys-lighting-bath-and-hardware have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.farreys.com/shop-all-lighting, https://www.farreys.com/shop-all-bath, https://www.farreys.com/shop-all-kitchen and https://www.farreys.com/shop-all-decorative-hardware 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.farreys.com/shop-all-brands took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

2 to fixGoogle 9287
  • 6 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 351 words of copy

    The homepage carries about 351 words of visible text.

6 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us” and “Join Trade Program”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Phone number on the homepage

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

  • 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
  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on farreys.com, including 23 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