Website review, no card needed

mooreandgiles.com logo

mooreandgiles.com website review

Visit site (opens in a new tab)Reviewed 21 October 202633 issues · 85 checks

This review found 33 issues worth fixing on mooreandgiles.com, 19 of them high impact, across 85 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
2.5 s2.1 sMay 2Oct 172.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.3 s
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
130 ms104 msMay 2Oct 17119 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026107 ms
May 9, 2026110 ms
May 16, 2026108 ms
May 23, 2026108 ms
May 30, 2026112 ms
Jun 6, 2026112 ms
Jun 13, 2026116 ms
Jun 20, 2026119 ms
Jun 27, 2026123 ms
Jul 4, 2026127 ms
Jul 11, 2026121 ms
Jul 18, 2026120 ms
Jul 25, 2026118 ms
Aug 1, 2026114 ms
Aug 8, 2026114 ms
Aug 15, 2026113 ms
Aug 22, 2026110 ms
Aug 29, 2026109 ms
Sep 5, 2026111 ms
Sep 12, 2026112 ms
Sep 19, 2026115 ms
Sep 26, 2026120 ms
Oct 3, 2026119 ms
Oct 10, 2026119 ms
Oct 17, 2026119 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 mooreandgiles.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mooreandgiles.com at 0.9 s0.9 s
  2. mooreandgiles.com at 1.9 s1.9 s
  3. mooreandgiles.com at 2.8 s2.8 s
  4. mooreandgiles.com at 3.8 s3.8 s
  5. mooreandgiles.com at 4.7 s4.7 s
  6. mooreandgiles.com at 5.7 s5.7 s
  7. mooreandgiles.com at 6.6 s6.6 s
  8. mooreandgiles.com at 7.6 s7.6 s

Speed

11 to fix34
  • Improve image delivery

    47.5 s · 23.9 MB

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

  • Reduce unused JavaScript

    9.7 s · 2.1 MB

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

  • Avoid multiple page redirects

    6.9 s

    The page goes through 1 redirect before it starts loading, costing about 6.9 s. Link and advertise the final URL directly.

  • Use efficient cache lifetimes

    2.1 s · 909 KiB

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

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 7.6 s

    A phone's processor spends 7.6 s on main-thread work while loading, 4.1 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 (Google Tag Manager, Accessibe Accessibility Overlay and Bigcommerce and others), adding 28.9 MB and 1.0 s of main-thread time.

  • Bigcommerce adds 149 ms

    149 ms

    Bigcommerce costs a phone 149 ms of main-thread work and 27.3 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.

  • Render-blocking requests

    700 ms

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

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 340 ms

    340 ms

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

    150 ms · 56 KiB

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

  • Minify JavaScript

    150 ms · 24 KiB

    24 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • Reduce unused CSS

    30 KiB

    About 30 KiB of CSS is downloaded but never applied on this page.

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

    13 ms

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

Core Web Vitals

8 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 CLS: 0.91

    0.91

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

  • First Contentful Paint: 9.1 s

    9.1 s

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

  • Largest Contentful Paint: 167.9 s

    167.9 s

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

  • Speed Index: 51.5 s

    51.5 s

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

  • Time to Interactive: 185.2 s

    185.2 s

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

  • Total Blocking Time: 901 ms

    901 ms

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

  • 10 images without width and height

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

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

    +10%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 121 ms

    121 ms

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

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

  • Real-user TTFB: 323 ms

    323 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 60.7 MB in 325 requests

    60.7 MB

    Your homepage downloads 60.7 MB in 325 requests on a phone: images 54.6 MB (88), scripts 4.8 MB (127) and fonts 682 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • About 17.2 g of CO₂ per visit

    17.20 g

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

3 checks passed
  • 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

6 to fixGoogle 9092
  • 2 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 image without alt text

    1 image has 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.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 8588
  • No H1 headline

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

  • 2 links crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 41 internal links, 10 external

    The homepage links to 41 pages on mooreandgiles.com and 10 external pages.

6 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Shop premium leather goods and American-made furniture from Moore & Giles. Furniture is handcrafted in the USA with exc…”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Moore & Giles | Leather Goods & Furniture”.

  • Canonical URL set

    The canonical URL is https://mooreandgiles.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.mooreandgiles.com/xmlsitemap.php.

AI search readiness

100
  • No llms.txt

    There is no https://mooreandgiles.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.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles) and description; logo and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (473 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 9 pages without a meta description

    https://mooreandgiles.com/contact-us, https://mooreandgiles.com/new-arrivals, https://mooreandgiles.com/limited-whipstich-welden-clutch, https://mooreandgiles.com/annie-crossbody, https://mooreandgiles.com/limited-marinos-small-zip-pouch and https://mooreandgiles.com/seven-hills-sydney-clutch and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://mooreandgiles.com/catalog has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://mooreandgiles.com/contact-us has 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.

  • 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

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

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

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187104929&tm=gtm002&Ver=2&mid=d8d969f4-39d9-4a22-b045-f3c2c1391b94&bo=1&sid=ac08d030cd4111f191e6b58d6223ac48&vid=ac0906e0cd4111f19b5a0f9f40050258&vids=0&msclkid=N&gtm_.

  • 4 small tap targets

    4 of 20 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 “Target is not a valid Node”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 450 words of copy

    The homepage carries about 450 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: “SHOP NEW ARRIVALS →” and “Shop Limited Whipstitched Welden Clutch”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “contact”, “Contact Us” and “Shop New Arrivals →”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 3 customer or partner logos.

  • Analytics in place

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

  • Direct contact links

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

Privacy and tracking

  • 9 trackers load before any consent

    9

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

  • 36 cookies set on arrival

    36

    Opening the homepage sets 36 cookies (measured from a US location before any click).

  • 65 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

E-commerce
BigCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
Linode;Cloudflare Hosting

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on mooreandgiles.com, including 19 speed issues and 2 SEO issues. 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