Website review, no card needed

mycustomchairs.com logo

mycustomchairs.com website review

Visit site (opens in a new tab)Reviewed 6 November 202645 issues · 90 checks

This review found 45 issues worth fixing on mycustomchairs.com, 18 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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

Full-page screenshot of mycustomchairs.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mycustomchairs.com at 0.4 s0.4 s
  2. mycustomchairs.com at 0.8 s0.8 s
  3. mycustomchairs.com at 1.1 s1.1 s
  4. mycustomchairs.com at 1.5 s1.5 s
  5. mycustomchairs.com at 1.9 s1.9 s
  6. mycustomchairs.com at 2.3 s2.3 s
  7. mycustomchairs.com at 2.6 s2.6 s
  8. mycustomchairs.com at 3.0 s3.0 s

Speed

13 to fix35
  • Reduce unused JavaScript

    4.3 s · 1.3 MB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 4.5 s

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

  • Improve image delivery

    200 ms · 2.3 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 3.2 MB and 1.8 s of main-thread time.

  • Use efficient cache lifetimes

    800 ms · 504 KiB

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

  • Reduce unused CSS

    900 ms · 189 KiB

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

  • YouTube adds 638 ms

    638 ms

    YouTube costs a phone 638 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.

  • Google Tag Manager adds 479 ms

    479 ms

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

  • Facebook adds 310 ms

    310 ms

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

  • rebuyengine.com adds 224 ms

    224 ms

    rebuyengine.com costs a phone 224 ms of main-thread work and 646 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.

  • Shopify adds 56 ms

    56 ms

    Shopify costs a phone 56 ms of main-thread work and 467 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.

  • 18 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    61 KiB

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

  • Font display

    50 ms

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

  • 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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix43
  • Largest Contentful Paint: 23.1 s

    23.1 s

    Your largest element takes 23.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Custom Adirondack Chairs Create your own custom Chair Get S…”.

  • Time to Interactive: 32.9 s

    32.9 s

    The page becomes fully interactive after 32.9 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: 11.2 s

    11.2 s

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

  • Total Blocking Time: 933 ms

    933 ms

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

  • 43 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 7.2 MB in 236 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 236 requests on a phone: images 3.2 MB (27), scripts 2.7 MB (83) and other files 727 KiB (94). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    3.5 MB

    5 images are downloaded at several times the size a phone draws them, for example FoldingAnimated_BlackChair_NewTag.gif at 1,451 px wide, shown at 355 px. Resized copies would save about 3.5 MB.

  • 2 images in older formats

    2 images (3.7 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.

  • 5 images below the first screen load straight away

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

  • About 2.0 g of CO₂ per visit

    2.03 g

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

Accessibility

9 to fixGoogle 7887
  • 19 text elements with low contrast

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

  • ARIA toggle fields must have an accessible name (5 elements)

    ARIA toggle fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (4 elements)

    Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 35 images without alt text

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

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

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

  • Zoom is disabled

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

  • 38 links without text

    38 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

Google 92100
  • No X (Twitter) card tag

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

  • 114 internal links, 15 external

    The homepage links to 114 pages on mycustomchairs.com and 15 external pages.

8 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Create your own custom Chair- Our chairs are different, 3/4" Traditional Adirondack Curved Back Style and Stainless Ste…”.

  • One H1 headline

    Your main headline reads: “Custom Adirondack Chairs”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Everything you need all in one spot! – My Custom Chairs”.

  • Canonical URL set

    The canonical URL is https://www.mycustomchairs.com/en-us.

  • Structured data in place

    Structured data found: LocalBusiness and WebSite.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

5 to fix76
  • 4 pages share 2 titles

    https://www.mycustomchairs.com/en-us and / all use the title “Everything you need all in one spot! – My Custom Chairs”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://www.mycustomchairs.com/en-us/collections/deep-seating, https://www.mycustomchairs.com/en-us/collections/adirondack-chairs, https://www.mycustomchairs.com/en-us/collections/bar-sets, https://www.mycustomchairs.com/en-us/collections/dining-sets, https://www.mycustomchairs.com/en-us/collections/picnic-tables and https://www.mycustomchairs.com/en-us/collections/outdoor-games and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    / and https://www.mycustomchairs.com/collections use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.mycustomchairs.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://www.mycustomchairs.com/en-us/collections/deep-seating, https://www.mycustomchairs.com/en-us/collections/adirondack-chairs, https://www.mycustomchairs.com/en-us/collections/bar-sets, https://www.mycustomchairs.com/en-us/collections/dining-sets, https://www.mycustomchairs.com/en-us/collections/picnic-tables and https://www.mycustomchairs.com/en-us/collections/outdoor-games and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.mycustomchairs.com/en-us/collections/bar-sets, https://www.mycustomchairs.com/en-us/collections/dining-sets and https://www.mycustomchairs.com/en-us/collections/picnic-tables 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.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 7391
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://gdata.youtube.com/feeds/api/videos/PBsQJpHOBWg?v=2&alt=json' from origin 'https://…”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    41 of 44 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

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

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

    The homepage carries about 417 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 Now” and “Get Started Now”.

  • 31 calls to action

    The homepage has 31 calls to action, for example “CONTACT”, “Shop Captain Chair” and “Shop Fire Pits”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 mycustomchairs.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Sb Countdown Timer Bar · klaviyo.com · onrender.com · rebuyengine.com · useifsapp.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

Stack

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on mycustomchairs.com, including 19 speed 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