Website review, no card needed

oldbrickfurniture.com logo

oldbrickfurniture.com website review

Visit site (opens in a new tab)Reviewed 24 October 202648 issues · 92 checks

This review found 48 issues worth fixing on oldbrickfurniture.com, 20 of them high impact, across 92 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
4.7 s3.0 sMay 2Oct 173.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.4 s
May 9, 20264.3 s
May 16, 20264.4 s
May 23, 20264.4 s
May 30, 20264.5 s
Jun 6, 20264.5 s
Jun 13, 20264.5 s
Jun 20, 20264.5 s
Jun 27, 20264.5 s
Jul 4, 20264.4 s
Jul 11, 20264.3 s
Jul 18, 20264.1 s
Jul 25, 20263.9 s
Aug 1, 20263.8 s
Aug 8, 20263.6 s
Aug 15, 20263.5 s
Aug 22, 20263.4 s
Aug 29, 20263.3 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
145 ms118 msMay 2Oct 17142 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026121 ms
May 9, 2026122 ms
May 16, 2026124 ms
May 23, 2026122 ms
May 30, 2026121 ms
Jun 6, 2026124 ms
Jun 13, 2026128 ms
Jun 20, 2026129 ms
Jun 27, 2026136 ms
Jul 4, 2026137 ms
Jul 11, 2026133 ms
Jul 18, 2026131 ms
Jul 25, 2026130 ms
Aug 1, 2026129 ms
Aug 8, 2026135 ms
Aug 15, 2026137 ms
Aug 22, 2026137 ms
Aug 29, 2026138 ms
Sep 5, 2026138 ms
Sep 12, 2026137 ms
Sep 19, 2026138 ms
Sep 26, 2026138 ms
Oct 3, 2026140 ms
Oct 10, 2026141 ms
Oct 17, 2026142 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 oldbrickfurniture.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. oldbrickfurniture.com at 0.6 s0.6 s
  2. oldbrickfurniture.com at 1.3 s1.3 s
  3. oldbrickfurniture.com at 1.9 s1.9 s
  4. oldbrickfurniture.com at 2.5 s2.5 s
  5. oldbrickfurniture.com at 3.1 s3.1 s
  6. oldbrickfurniture.com at 3.7 s3.7 s
  7. oldbrickfurniture.com at 4.4 s4.4 s
  8. oldbrickfurniture.com at 5.0 s5.0 s

Speed

13 to fix29
  • Use efficient cache lifetimes

    3.4 s · 9.9 MB

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

  • Improve image delivery

    2.3 s · 8.0 MB

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

  • Render-blocking requests

    2.0 s

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

  • Mobile performance score: 29

    29/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and JSDelivr CDN and others), adding 2.4 MB and 1.4 s of main-thread time.

  • Reduce unused JavaScript

    310 ms · 912 KiB

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

  • Reduce unused CSS

    770 ms · 144 KiB

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

  • Google Tag Manager adds 584 ms

    584 ms

    Google Tag Manager costs a phone 584 ms of main-thread work and 700 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: 3.4 s

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

  • Facebook adds 253 ms

    253 ms

    Facebook costs a phone 253 ms of main-thread work and 283 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.

  • 13 long tasks on the main thread

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

  • Attentive adds 59 ms

    59 ms

    Attentive costs a phone 59 ms of main-thread work and 766 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.

  • Google CDN adds 95 ms

    95 ms

    Google CDN costs a phone 95 ms of main-thread work and 348 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.

  • Legacy JavaScript

    65 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 70 but mobile only 29. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 37 ms

    37 ms

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

Core Web Vitals

10 to fix100
  • 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: 27.1 s

    27.1 s

    Your largest element takes 27.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “6 Hour Clearance Event EXTENDED! - Save up to 70% OFF!”.

  • Time to Interactive: 35.2 s

    35.2 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • Cumulative Layout Shift: 0.343

    0.343

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

  • Total Blocking Time: 659 ms

    659 ms

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

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

  • 31 images without width and height

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

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

    +16%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 154 ms

    154 ms

    Real visitors wait 154 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.

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

    -22%

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

Images and page weight

4 to fix28
  • Page weight: 12.1 MB in 196 requests

    12.1 MB

    Your homepage downloads 12.1 MB in 196 requests on a phone: images 9.4 MB (48), scripts 2.3 MB (65) and stylesheets 197 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 6.9 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    2.8 MB

    2 images are downloaded at several times the size a phone draws them, for example a1feb0defff2080b4020046bddabbea3.webp at 1,664 px wide, shown at 375 px. Resized copies would save about 2.8 MB.

  • 5 images below the first screen load straight away

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

  • About 3.4 g of CO₂ per visit

    3.43 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8990
  • 1 button without a name

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

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

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

  • 2 images without alt text

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

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 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 9275
  • No H1 headline

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

  • Title is long (93 characters)

    Your title is 93 characters, so Google will cut it off around 60: “Old Brick | Furniture & Mattress Store in NY, VT, and MA | Old Brick Furniture & Mattress…”.

  • Meta description is long (262 characters)

    Your meta description is 262 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 10 links crawlers can't follow

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 232 internal links, 10 external

    The homepage links to 232 pages on oldbrickfurniture.com and 10 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList and FurnitureStore.

  • 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.oldbrickfurniture.com/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.

3 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 (673 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.oldbrickfurniture.com/llms.txt (4 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix75
  • 1 linked page is broken

    Your homepage links to https://www.oldbrickfurniture.com/the-old-brick-difference, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 15 internal pages checked

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

6 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 11 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7787
  • 20 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

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

  • About 312 words of copy

    The homepage carries about 312 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 17 calls to action

    The homepage has 17 calls to action, for example “Call Us”, “LEARN MORE ►” and “Shop all departments ►”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

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

    7

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

  • 28 cookies set on arrival

    28

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

  • 45 other companies contacted

    Loading the homepage contacts 45 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 oldbrickfurniture.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
KnorrWeb V5
Framework
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on oldbrickfurniture.com, including 23 speed issues, 5 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