Website review, no card needed
echoparkspeedway.com website review
Visit site (opens in a new tab)Reviewed 22 October 202640 issues · 95 checks
This review found 40 issues worth fixing on echoparkspeedway.com, 17 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 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.4 s |
| Aug 8, 2026 | 1.4 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.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 144 ms |
| May 9, 2026 | 150 ms |
| May 16, 2026 | 159 ms |
| May 23, 2026 | 153 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 158 ms |
| Jun 20, 2026 | 159 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 142 ms |
| Aug 8, 2026 | 140 ms |
| Aug 15, 2026 | 161 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 186 ms |
| Oct 17, 2026 | 186 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
Reduce unused JavaScript
15.2 s · 3.0 MBAbout 3.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 15.2 s faster on a phone.
Use efficient cache lifetimes
12.5 s · 2.5 MB134 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).
Render-blocking requests
5.4 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.4 s.
Reduce unused CSS
1.1 s · 232 KiBAbout 232 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, gofevo.com and rlets.com and others), adding 4.9 MB and 1.3 s of main-thread time.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 762 ms. During a long task the page ignores taps.
gofevo.com adds 248 ms
248 msgofevo.com costs a phone 248 ms of main-thread work and 3.0 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.
Legacy JavaScript
350 ms · 54 KiBPolyfills for old browsers add 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Google Tag Manager adds 305 ms
305 msGoogle Tag Manager costs a phone 305 ms of main-thread work and 673 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 168 ms
168 msFacebook costs a phone 168 ms of main-thread work and 314 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.
Google Maps adds 95 ms
95 msGoogle Maps costs a phone 95 ms of main-thread work and 384 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.
Improve image delivery
250 ms · 228 KiB17 images could be 228 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Minify JavaScript
170 ms · 60 KiB60 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 27 KiB27 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 64 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 19.9 s
19.9 sThe first text or image appears after 19.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 41.2 s
41.2 sYour largest element takes 41.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Autotrader 400 Feb. 27-28, 2027 PURCHASE TICKETS EVENT INFO”.
Speed Index: 19.9 s
19.9 sVisually, the page fills in at 19.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 49.2 s
49.2 sThe page becomes fully interactive after 49.2 s. Good is under 3.8 s.
Total Blocking Time: 776 ms
776 msScripts block taps and scrolling for 776 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 144 ms to 186 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.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 this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 195 ms
195 msReal visitors wait 195 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (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: 354 ms
354 msReal visitors wait 354 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).
Images and page weight
Page weight: 7.9 MB in 317 requests
7.9 MBYour homepage downloads 7.9 MB in 317 requests on a phone: scripts 5.6 MB (68), images 846 KiB (88) and fonts 599 KiB (8). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (70 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.
6 images below the first screen load straight away
6 images further down the page (175 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.2 g of CO₂ per visit
2.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.23 g of CO₂e: 268.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
21 tap targets too small
21 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
All page content should be contained by landmarks (43 elements)
All page content should be contained by landmarks: 43 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (6 elements).
2 checks passed
Every image has alt text
All 69 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 8 failed. 7 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
104 internal links, 92 external
The homepage links to 104 pages on echoparkspeedway.com and 92 external pages.
8 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Enjoy NASCAR events, races, concerts, and entertainment at EchoPark Speedway. Enjoy unforgettable racing and fan experi…”.
One H1 headline
Your main headline reads: “Autotrader 400”.
Title: 52 characters
Your title is a healthy 52 characters: “EchoPark Speedway: NASCAR Tickets, Events & Schedule”.
Canonical URL set
The canonical URL is https://www.echoparkspeedway.com/.
Structured data in place
Structured data found: 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.atlantamotorspeedway.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.echoparkspeedway.com/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.
2 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 (849 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 60 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
13 third-party cookies
13 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
36 of 44 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
About 523 words of copy
The homepage carries about 523 words of visible text.
5 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Gift Shop”, “Buy Tickets Now!” and “Reserve Your Spot”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
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.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
57 other companies contacted
Loading the homepage contacts 57 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 echoparkspeedway.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on echoparkspeedway.com, including 20 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.