Website review, no card needed
genuinereplacementparts.com website review
Visit site (opens in a new tab)Reviewed 4 November 202639 issues · 99 checks
This review found 39 issues worth fixing on genuinereplacementparts.com, 15 of them high impact, across 99 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83B- #28,549 of 125,753 reviewed websitesbeats 72%
- #18,537 of 70,254 online storesbeats 67%
- #17,943 of 63,820 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 148 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 147 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 153 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 155 ms |
| Oct 3, 2026 | 155 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 153 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
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.0 s
5.0 s
6.0 s
7.0 s
8.0 s
Speed
Render-blocking requests
2.0 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
audioeye.com adds 1.6 s
1.6 saudioeye.com costs a phone 1.6 s of main-thread work and 298 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.3 s
A phone's processor spends 9.3 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,687 HTML elements
The page has 4,687 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, Google Tag Manager and logr-in.com and others), adding 1.4 MB and 2.5 s of main-thread time.
Reduce unused JavaScript
300 ms · 914 KiBAbout 914 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
450 ms · 140 KiBAbout 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 405 ms
405 msGoogle Tag Manager costs a phone 405 ms of main-thread work and 514 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.
Use efficient cache lifetimes
150 ms · 296 KiB34 files are served with short cache lifetimes, so returning visitors download them again (296 KiB).
Duplicated JavaScript
300 ms · 56 KiB56 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 218 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 10 KiB10 KiB could be saved by minifying CSS.
Improve image delivery
155 KiB11 images could be 155 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
58 KiB58 KiB could be saved by minifying JavaScript.
Legacy JavaScript
55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need.
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: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.7 s
11.7 sYour largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 28.6 s
28.6 sThe page becomes fully interactive after 28.6 s. Good is under 3.8 s.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 562 ms
562 msScripts block taps and scrolling for 562 ms in total while the page loads. Good is under 200 ms.
16 images without width and height
16 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-10-31, real Chrome visitors' tap response (inp) went from 148 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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 LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 133 ms
133 msReal visitors wait 133 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 728 ms
728 msReal visitors wait 728 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.049
0.049The layout barely moves while loading (CLS 0.049, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 363 requests
5.7 MBYour homepage downloads 5.7 MB in 363 requests on a phone: scripts 2.3 MB (129), images 1.6 MB (105) and other files 873 KiB (81). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
appliance_banner_39a9d394-fdd5-4937-beb9-a21bf0135916.svg weighs 1.2 MB. On a phone connection a single image that size takes seconds.
2 images in older formats
2 images (439 KiB) 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.
4 images below the first screen load straight away
4 images further down the page (106 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 193.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
223 images without alt text
223 images have no alt text, which hurts accessibility and image search.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
<marquee> elements are deprecated and must not be used (1 element)
<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (21 elements)
All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.
28 links without text
28 visible links have no text or label, so screen readers cannot say where they go.
16 form fields without a label
16 form fields have no label, so screen readers announce an empty box and autofill guesses.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (1 element).
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
494 internal links, 47 external
The homepage links to 494 pages on genuinereplacementparts.com and 47 external pages.
7 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Genuine Replacement Parts stocks OEM parts from top manufacturers. Use model-based search and diagrams to find exactly …”.
One H1 headline
Your main headline reads: “Genuine Appliance Parts. Unbeatable Value.”.
Title: 60 characters
Your title is a healthy 60 characters: “Genuine Replacement parts: Genuine OEM Parts and Accessories”.
Canonical URL set
The canonical URL is https://genuinereplacementparts.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://genuinereplacementparts.com/apps/sitemap1/sitemap_index.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (4,355 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://genuinereplacementparts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://genuinereplacementparts.com/collections/refrigerator, which answers with an error. Visitors hit a dead end and search engines drop it.
7 pages share a meta description
https://genuinereplacementparts.com/pages/price-match, https://genuinereplacementparts.com/pages/track-order, https://genuinereplacementparts.com/pages/contact, https://genuinereplacementparts.com/pages/technician-cart, https://genuinereplacementparts.com/pages/brand and https://genuinereplacementparts.com/pages/brand-category and 1 other use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://genuinereplacementparts.com/collections/lg-water-filters, whose canonical is https://genuinereplacementparts.com/collections/lg-refrigerator-water-filters. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://genuinereplacementparts.com/collections/lg-water-filters, https://genuinereplacementparts.com/pages/track-order, https://genuinereplacementparts.com/pages/technician-cart, https://genuinereplacementparts.com/collections/water-filters-2, https://genuinereplacementparts.com/collections/washer and https://genuinereplacementparts.com/collections/dryer and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://genuinereplacementparts.com/collections/washer and https://genuinereplacementparts.com/collections/microwave took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 167 found) and read each the way a search engine does.
4 checks passed
Every page has a meta description
All 14 pages that loaded have a meta description.
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
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Identifier 'marquee' has already been declared”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
76 of 85 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 643 words of copy
The homepage carries about 643 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Track Your Order” and “Shop By Brand”.
25 calls to action
The homepage has 25 calls to action, for example “Track Your Order”, “Contact Us” and “Signup”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 34 testimonial or review blocks, a star rating, 33 trust badges and “295,810 + reviews”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 4 phone links and 2 email links.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
25 cookies set on arrival
25Opening the homepage sets 25 cookies (measured from a US location before any click).
46 other companies contacted
Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 genuinereplacementparts.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Seal Subscriptions · Klaviyo Email Marketing Sms · Microsoft Clarity · 56071677a62720b5cde4241477474f626e61c35a · richpanel.com · trustpilot.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 Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on genuinereplacementparts.com, including 18 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.