Website review, no card needed
4lifetimelines.com website review
Visit site (opens in a new tab)Reviewed 28 October 202629 issues · 80 checks
This review found 29 issues worth fixing on 4lifetimelines.com, 10 of them high impact, across 80 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
81B- #39,852 of 118,247 reviewed websitesbeats 61%
- #26,615 of 67,198 online storesbeats 54%
- #25,672 of 61,274 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 161 ms |
| May 16, 2026 | 157 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 151 ms |
| Jun 27, 2026 | 159 ms |
| Jul 4, 2026 | 156 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 148 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 136 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 139 ms |
| Aug 29, 2026 | 145 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 158 ms |
| Sep 26, 2026 | 161 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 160 ms |
| Oct 24, 2026 | 161 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.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
2.8 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Reduce unused JavaScript
1.4 s · 496 KiBAbout 496 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
800 ms · 175 KiB14 files are served with short cache lifetimes, so returning visitors download them again (175 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Clarity and occ-app.com and others), adding 1.2 MB and 464 ms of main-thread time.
Improve image delivery
450 ms · 71 KiB2 images could be 71 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
380 ms · 131 KiBAbout 131 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 380 ms faster on a phone.
Legacy JavaScript
300 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Klaviyo adds 200 ms
200 msKlaviyo costs a phone 200 ms of main-thread work and 518 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: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,662 HTML elements
The page has 1,662 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 63 ms. During a long task the page ignores taps.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.26
0.26For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 15.9 s
15.9 sYour largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 7.5 s
7.5 sThe first text or image appears after 7.5 s on a phone. Good is under 1.8 s.
Time to Interactive: 16.1 s
16.1 sThe page becomes fully interactive after 16.1 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 161 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 124 ms
124 msReal visitors wait 124 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 777 ms
777 msReal visitors wait 777 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.5 MB in 184 requests
2.5 MBYour homepage downloads 2.5 MB in 184 requests on a phone: scripts 1.2 MB (101), fonts 540 KiB (8) and other files 316 KiB (40). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.72 g of CO₂e: 85.8 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
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.
2 checks passed
Every image has alt text
All 83 images in the HTML carry an alt attribute.
57 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: 57 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
193 internal links, 3 external
The homepage links to 193 pages on 4lifetimelines.com and 3 external pages.
8 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Discover rust proof copper nickel brake lines, pre bent kits, fittings and tools that bend easily and install fast. Lif…”.
One H1 headline
Your main headline reads: “Brake lines that never rust.”.
Title: 63 characters
Your title is a healthy 63 characters: “4LifetimeLines: Rust Proof Brake Lines & Kits for Pros & DIYers”.
Canonical URL set
The canonical URL is https://4lifetimelines.com/.
Structured data in place
Structured data found: AutoPartsStore, Organization, WebPage 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://4lifetimelines.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: 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 (1,707 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://4lifetimelines.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://4lifetimelines.com/a/store-locator/list, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://4lifetimelines.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://4lifetimelines.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://4lifetimelines.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://4lifetimelines.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 88 found) and read each the way a search engine does.
2 checks passed
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.
Best practices
22 small tap targets
22 of 62 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.occ-app.com/shopify-apps/one-click-checkout/common.css' from origin 'https://4…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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 1,460 words of copy
The homepage carries about 1,460 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP BRAKE LINES”.
25 calls to action
The homepage has 25 calls to action, for example “Shop by Vehicle”, “Shop All Shop by Vehicle” and “Shop All Brake Lines”.
20 short forms
20 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 57 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and HubSpot.
Direct contact links
Visitors can reach you directly: 5 phone links and 1 email link.
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 Meta Pixel and 2 mores (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
30 other companies contacted
Loading the homepage contacts 30 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 4lifetimelines.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- 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 29 issues on 4lifetimelines.com, including 17 speed 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.