Website review, no card needed
sonyparts.com website review
Visit site (opens in a new tab)Reviewed 9 November 202620 issues · 66 checks
This review found 20 issues worth fixing on sonyparts.com, 4 of them high impact, across 66 checks. The most urgent: 1 text element with low contrast. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 580 ms |
| May 30, 2026 | 538 ms |
| Jun 6, 2026 | 549 ms |
| Jun 13, 2026 | 519 ms |
| Jun 20, 2026 | 529 ms |
| Jun 27, 2026 | 551 ms |
| Jul 4, 2026 | 535 ms |
| Jul 11, 2026 | 527 ms |
| Jul 18, 2026 | 488 ms |
| Jul 25, 2026 | 246 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 130 ms |
| Aug 15, 2026 | 114 ms |
| Aug 22, 2026 | 110 ms |
| Aug 29, 2026 | 111 ms |
| Sep 5, 2026 | 108 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 110 ms |
| Oct 3, 2026 | 111 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 116 ms |
| Oct 24, 2026 | 118 ms |
| Oct 31, 2026 | 119 ms |
| Nov 7, 2026 | 116 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
Speed
Not measured in this review.
Core Web Vitals
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.4 s 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 your site (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 116 ms
116 msReal visitors wait 116 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 610 ms
610 msReal visitors wait 610 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 79% faster for real visitors
-79%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 580 ms to 116 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 2.4 MB
2.4 MBYour homepage downloads 2.4 MB on a phone, 192 KiB of it images (8%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Logo_37_x250.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image in older formats
1 image (37 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (37 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 82.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (72 characters)
Your title is 72 characters, so Google will cut it off around 60: “Sony Replacement Parts | Original Spare Parts & Accessories — Sony Parts”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
111 internal links, 2 external
The homepage links to 111 pages on sonyparts.com and 2 external pages.
6 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “Get the genuine replacement at great prices with fast shipping. Keep your Sony products running smoothly!”.
One H1 headline
Your main headline reads: “Sony Replacement Parts”.
Canonical URL set
The canonical URL is https://sonyparts.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://sonyparts.com/sitemap.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (963 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://sonyparts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://sonyparts.com/collections declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
7 pages without a meta description
https://sonyparts.com/pages/contact-us, https://sonyparts.com/pages/order-status, https://sonyparts.com/collections/televisions-accessories, https://sonyparts.com/collections/3d-glasses, https://sonyparts.com/collections/remote-control and https://sonyparts.com/collections/all-home-video and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
https://sonyparts.com/collections, https://sonyparts.com/collections/all-tvs, https://sonyparts.com/collections/lcd-tv, https://sonyparts.com/collections/led-tvs, https://sonyparts.com/collections/blu-ray-disc-players and https://sonyparts.com/collections/dvd-players and 2 others use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://sonyparts.com/pages/contact-us and https://sonyparts.com/pages/order-status have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://sonyparts.com/collections/all-tvs took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 87 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'appendChild')”.
2 checks passed
Tap targets are thumb-sized
46 of 54 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.
Thin social proof
Social proof on the homepage: 9 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 228 words
The homepage has only about 228 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Support” and “Order Status”.
11 calls to action
The homepage has 11 calls to action, for example “Contact Support”, “Order Status” and “Quick Shop”.
6 short forms
6 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).
40 other companies contacted
Loading the homepage contacts 40 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 sonyparts.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
Microsoft Clarity · Cartbite · Simple Social Login · richpanel.com · sealsubscriptions.com · nfcube.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 | 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 20 issues on sonyparts.com, including 1 speed issue, 2 SEO 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.