Website review, no card needed

marlofurniture.com logo

marlofurniture.com website review

Visit site (opens in a new tab)Reviewed 10 November 202644 issues · 88 checks

This review found 44 issues worth fixing on marlofurniture.com, 20 of them high impact, across 88 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
789 ms613 msMay 23Nov 7694 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026694 ms
May 30, 2026683 ms
Jun 6, 2026666 ms
Jun 13, 2026672 ms
Jun 20, 2026676 ms
Jun 27, 2026696 ms
Jul 4, 2026684 ms
Jul 11, 2026701 ms
Jul 18, 2026639 ms
Jul 25, 2026633 ms
Aug 1, 2026648 ms
Aug 8, 2026639 ms
Aug 15, 2026670 ms
Aug 22, 2026718 ms
Aug 29, 2026718 ms
Sep 5, 2026764 ms
Sep 12, 2026762 ms
Sep 19, 2026686 ms
Sep 26, 2026724 ms
Oct 3, 2026762 ms
Oct 10, 2026749 ms
Oct 17, 2026769 ms
Oct 24, 2026727 ms
Oct 31, 2026684 ms
Nov 7, 2026694 ms
Real-visitor tap response (INP)75th percentile, phones
81 ms61 msMay 23Nov 779 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202677 ms
May 30, 202678 ms
Jun 6, 202676 ms
Jun 13, 202675 ms
Jun 20, 202674 ms
Jun 27, 202677 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202674 ms
Jul 25, 202674 ms
Aug 1, 202671 ms
Aug 8, 202671 ms
Aug 15, 202672 ms
Aug 22, 202671 ms
Aug 29, 202671 ms
Sep 5, 202671 ms
Sep 12, 202670 ms
Sep 19, 202663 ms
Sep 26, 202663 ms
Oct 3, 202673 ms
Oct 10, 202673 ms
Oct 17, 202679 ms
Oct 24, 202679 ms
Oct 31, 202679 ms
Nov 7, 202679 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 marlofurniture.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. marlofurniture.com at 0.6 s0.6 s
  2. marlofurniture.com at 1.3 s1.3 s
  3. marlofurniture.com at 1.9 s1.9 s
  4. marlofurniture.com at 2.6 s2.6 s
  5. marlofurniture.com at 3.2 s3.2 s
  6. marlofurniture.com at 3.9 s3.9 s
  7. marlofurniture.com at 4.5 s4.5 s
  8. marlofurniture.com at 5.1 s5.1 s

Speed

13 to fix28
  • Use efficient cache lifetimes

    4.5 s · 1.0 MB

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

  • Reduce unused JavaScript

    2.7 s · 1.2 MB

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

  • Render-blocking requests

    3.1 s

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

  • Mobile performance score: 28

    28/100

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

  • Main-thread work: 4.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (amaicdn.com, Google Tag Manager and getmorereviews.com and others), adding 2.6 MB and 2.1 s of main-thread time.

  • Improve image delivery

    350 ms · 1.5 MB

    15 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • 9 long tasks on the main thread

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

  • amaicdn.com adds 975 ms

    975 ms

    amaicdn.com costs a phone 975 ms of main-thread work and 508 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 Tag Manager adds 645 ms

    645 ms

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

    400 ms · 80 KiB

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

  • Reduce unused CSS

    300 ms · 136 KiB

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

  • getmorereviews.com adds 179 ms

    179 ms

    getmorereviews.com costs a phone 179 ms of main-thread work and 412 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.

  • Minify CSS

    150 ms · 41 KiB

    41 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • 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: 7 ms

    7 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 31.4 s

    31.4 s

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

  • Time to Interactive: 41.3 s

    41.3 s

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

  • First Contentful Paint: 6.4 s

    6.4 s

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

  • Speed Index: 12.3 s

    12.3 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • 33 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

4 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 CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

4 to fix28
  • Page weight: 9.8 MB in 438 requests

    9.8 MB

    Your homepage downloads 9.8 MB in 438 requests on a phone: images 5.3 MB (79), scripts 3.2 MB (131) and other files 798 KiB (176). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    campaign-freemont-set-desktop.jpg weighs 502 KiB. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    551 KiB

    5 images are downloaded at several times the size a phone draws them, for example campaign-freemont-set-mobile.jpg at 2,085 px wide, shown at 360 px. Resized copies would save about 551 KiB.

  • 19 images below the first screen load straight away

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

  • About 2.8 g of CO₂ per visit

    2.77 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.77 g of CO₂e: 332.4 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

10 to fixGoogle 6985
  • 23 tap targets too small

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

  • 2 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 45 images without alt text

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

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

    All page content should be contained by landmarks: 29 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.

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

  • 31 links without text

    31 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, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 8581
  • No H1 headline

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

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

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

  • 251 internal links, 10 external

    The homepage links to 251 pages on marlofurniture.com and 10 external pages.

5 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Shop Marlo Furniture for an amazing selection of Furniture & Mattress in the Alexandria, VA, Forestville, Laurel, Rockv…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Marlo Furniture | VA, MD, & DC Furniture & Mattress Store”.

  • Canonical URL set

    The canonical URL is https://www.marlofurniture.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.marlofurniture.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 (677 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 13 pages without a meta description

    https://www.marlofurniture.com/pages/financing, https://www.marlofurniture.com/collections/living-room, https://www.marlofurniture.com/collections/sofas, https://www.marlofurniture.com/collections/sectionals, https://www.marlofurniture.com/collections/reclining-loveseat and https://www.marlofurniture.com/collections/reclining-sofas and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.marlofurniture.com/pages/financing and https://www.marlofurniture.com/collections/living-room have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 to fixGoogle 9271
  • 5 broken images

    5 images failed to load on a phone, for example https://insight.adsrvr.org/track/pxl/?adv=hya02pi&ct=0:iknb1f3&fmt=3.

  • 12 small tap targets

    12 of 18 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: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 342 words of copy

    The homepage carries about 342 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: “TRACK YOUR ORDER”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “TRACK YOUR ORDER”, “LEARN MORE” and “TRACK ORDER”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and HubSpot.

  • Direct contact links

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

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies, 4 of them by other companies (measured from a US location before any click).

  • 68 other companies contacted

    Loading the homepage contacts 68 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 marlofurniture.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Access Pro · aaawebstore.com · chimpstatic.com · livechatinc.com · kudobuzz.com · klaviyo.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Company

Headquarters
Alexandria

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on marlofurniture.com, including 19 speed issues, 4 SEO issues and 1 conversion gap. 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