Website review, no card needed
1aauto.com website review
Visit site (opens in a new tab)Reviewed 11 October 202632 issues · 97 checks
This review found 32 issues worth fixing on 1aauto.com, 7 of them high impact, across 97 checks. The most urgent: 1 text element with low contrast. 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
86BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.2 s |
| Apr 25, 2026 | 1.2 s |
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 101 ms |
| Apr 25, 2026 | 101 ms |
| May 2, 2026 | 101 ms |
| May 9, 2026 | 103 ms |
| May 16, 2026 | 104 ms |
| May 23, 2026 | 109 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 116 ms |
| Jun 20, 2026 | 116 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 117 ms |
| Jul 11, 2026 | 117 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 117 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 120 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
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.9 s
3.3 s
1aauto.com does not allow embedding, so this is Google's rendering of the page.
Speed
Mobile performance score: 74
74/100Your mobile performance score is 74 (desktop: 75). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
911 KiBAbout 911 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
350 ms · 488 KiB33 files are served with short cache lifetimes, so returning visitors download them again (488 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Monetate and Other Google APIs/SDKs and others), adding 1.2 MB and 598 ms of main-thread time.
Google CDN adds 357 ms
357 msGoogle CDN costs a phone 357 ms of main-thread work and 733 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.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
300 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 293 ms. During a long task the page ignores taps.
Improve image delivery
239 KiB6 images could be 239 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
150 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
1 checks passed
Server response: 45 ms
45 msYour server sent the HTML in 45 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 16.9 s
16.9 sThe page becomes fully interactive after 16.9 s. Good is under 3.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 628 ms
628 msScripts block taps and scrolling for 628 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 2.7 s
2.7 sYour largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Shop Now”.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 101 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 143 ms
143 msReal visitors wait 143 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 793 ms
793 msReal visitors wait 793 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 86 requests
3.4 MBYour homepage downloads 3.4 MB in 86 requests on a phone: scripts 1.8 MB (29), images 944 KiB (21) and other files 393 KiB (23). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (765 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.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
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.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
15 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 16 WCAG 2.2 A/AA and best-practice rules on the phone render: 15 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.
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.
No XML sitemap
No XML sitemap at https://www.1aauto.com/sitemap.xml.gz, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
146 internal links, 8 external
The homepage links to 146 pages on 1aauto.com and 8 external pages.
5 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Let 1A Auto empower you to fix your car & save hundreds. More than quality auto parts! Auto Repair Video library. USA c…”.
One H1 headline
Your main headline reads: “1A Auto: Aftermarket Auto Parts Online Retailer”.
Title: 63 characters
Your title is a healthy 63 characters: “1A Auto | Aftermarket Car Parts - Buy Quality Auto Parts Online”.
Canonical URL set
The canonical URL is https://www.1aauto.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No llms.txt
There is no /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 url, logo, sameAs (social profiles) and contact details; name and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (909 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
/about/contact.html is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/about/contact.html and /tracking all use the title “1A Auto : Aftermarket Auto Parts, Car Body Parts, Replacement & New A…”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
/about/contact.html and /tracking use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example /videos.html, whose canonical is /videos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=4018190&Ver=2&mid=898deb68-5f40-47c2-be01-9a388628eab8&bo=1&sid=044735f0c5ac11f18e6bedcff0def334&vid=044714f0c5ac11f198517df192db461e&vids=1&msclkid=N&pi=918639831&lg=.
13 small tap targets
13 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
7 checks passed
Served over HTTPS
The homepage is served over HTTPS (1aauto.com).
Valid certificate (180 days left)
The certificate from DigiCert Inc · GeoTrust TLS RSA CA G1 verifies for 1aauto.com and is valid for another 180 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://1aauto.com redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 47 links work
All 47 links checked from your homepage (40 internal, 7 external) answered without errors.
Domain and trust
No CAA record
1aauto.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
1aauto.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 27 years old
27 years1aauto.com was registered in Jan 1999 through CSC Corporate Domains, Inc.. An established domain carries more trust with email providers and search engines.
Registered until Jan 2027
1aauto.com is registered until Jan 2027.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 161 words
The homepage has only about 161 words of visible text; thin pages give Google and first-time buyers little to go on.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop By Part” and “Shop By Make”.
17 calls to action
The homepage has 17 calls to action, for example “Sign In or Register”, “Track Order” and “Shop By”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Email authentication
SPF does not block other senders (no all)
Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=1aauto.com.hosted.spf-report.com”.
Email authentication score: 85/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication, and sends you reports.
DKIM signing found
A DKIM key is published (selector “k2”, “s1” and “s2”), so receivers can verify mail really came from you.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies (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.
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Go beyond the website
What your $25 Growth Playbook adds
This free review found 32 issues on 1aauto.com, including 13 speed issues, 3 SEO issues and 2 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.