Website review, no card needed
gforcepowersports.com website review
Visit site (opens in a new tab)Reviewed 7 November 202650 issues · 98 checks
This review found 50 issues worth fixing on gforcepowersports.com, 26 of them high impact, across 98 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
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 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 | 234 ms |
| May 23, 2026 | 244 ms |
| May 30, 2026 | 253 ms |
| Jun 6, 2026 | 256 ms |
| Jun 13, 2026 | 262 ms |
| Jun 20, 2026 | 255 ms |
| Jun 27, 2026 | 246 ms |
| Jul 4, 2026 | 245 ms |
| Jul 11, 2026 | 240 ms |
| Jul 18, 2026 | 237 ms |
| Jul 25, 2026 | 229 ms |
| Aug 1, 2026 | 219 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 229 ms |
| Aug 22, 2026 | 235 ms |
| Aug 29, 2026 | 262 ms |
| Sep 5, 2026 | 271 ms |
| Sep 12, 2026 | 262 ms |
| Sep 19, 2026 | 266 ms |
| Sep 26, 2026 | 257 ms |
| Oct 3, 2026 | 257 ms |
| Oct 10, 2026 | 262 ms |
| Oct 17, 2026 | 254 ms |
| Oct 24, 2026 | 246 ms |
| Oct 31, 2026 | 228 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
2.7 s
5.3 s
8.0 s
10.6 s
13.3 s
16.0 s
18.6 s
21.3 s
Speed
Reduce unused JavaScript
14.9 s · 3.1 MBAbout 3.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 14.9 s faster on a phone.
Improve image delivery
1.9 s · 4.4 MB109 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Use efficient cache lifetimes
3.5 s · 1.5 MB109 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Main-thread work: 39.4 s
A phone's processor spends 39.4 s on main-thread work while loading, 25.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 2.2 s
2.2 sGoogle Tag Manager costs a phone 2.2 s of main-thread work and 3.0 MB 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.
Render-blocking requests
2.5 s33 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Minify JavaScript
1.5 s · 282 KiB282 KiB could be saved by minifying JavaScript.
Google CDN adds 1.0 s
1.0 sGoogle CDN costs a phone 1.0 s of main-thread work and 775 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: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,198 HTML elements
The page has 5,198 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 (Google Tag Manager, Google CDN and Clarity and others), adding 6.4 MB and 4.9 s of main-thread time.
Reduce unused CSS
780 ms · 143 KiBAbout 143 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 780 ms faster on a phone.
Legacy JavaScript
600 ms · 139 KiBPolyfills for old browsers add 139 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 595 ms. During a long task the page ignores taps.
Clarity adds 488 ms
488 msClarity costs a phone 488 ms of main-thread work and 31 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 344 ms
344 msFacebook costs a phone 344 ms of main-thread work and 369 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.
shiftdigitalapps.io adds 352 ms
352 msshiftdigitalapps.io costs a phone 352 ms of main-thread work and 274 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Duplicated JavaScript
24 KiB24 KiB JavaScript is shipped twice across bundles.
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: 63 ms
63 msYour server sent the HTML in 63 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.76
0.76For real visitors the layout shifts by 0.76 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 102.4 s
102.4 sYour largest element takes 102.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 22.9 s
22.9 sVisually, the page fills in at 22.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 106.4 s
106.4 sThe page becomes fully interactive after 106.4 s. Good is under 3.8 s.
Total Blocking Time: 2.9 s
2.9 sScripts block taps and scrolling for 2.9 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.9 s
4.9 sThe first text or image appears after 4.9 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
34 images without width and height
34 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 234 ms to 228 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 190 ms
190 msReal visitors wait 190 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 722 ms
722 msReal visitors wait 722 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.2 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 29.1 MB in 581 requests
29.1 MBYour homepage downloads 29.1 MB in 581 requests on a phone: images 20.0 MB (266), scripts 7.5 MB (147) and other files 669 KiB (110). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
505 KiB3 images are downloaded at several times the size a phone draws them, for example IMC_2026_RHHE_DLR_US_HW25_1920x620.jpg at 1,920 px wide, shown at 375 px. Resized copies would save about 505 KiB.
1 image in older formats
1 image (433 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.
About 8.2 g of CO₂ per visit
8.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.25 g of CO₂e: 989.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
42 images without alt text
42 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (97 elements)
All page content should be contained by landmarks: 97 elements on the page fail this check, rated moderate by axe-core.
30 links without text
30 visible links have no text or label, so screen readers cannot say where they go.
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
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
316 internal links, 18 external
The homepage links to 316 pages on gforcepowersports.com and 18 external pages.
6 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Browse top brands, new & used inventory, parts, service, and financing at G-Force Powersports in Lakewood, CO—your one-…”.
Title: 58 characters
Your title is a healthy 58 characters: “G-Force Powersports | Motorcycles, ATVs & More in Lakewood”.
Canonical URL set
The canonical URL is https://www.gforcepowersports.com/.
Structured data in place
Structured data found: AutoDealer, AutomotiveBusiness, BreadcrumbList 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://www.gforcepowersports.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (6,358 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.gforcepowersports.com/llms.txt (3 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
6 pages share a title
https://www.gforcepowersports.com/inventory/featured-new-vehicles, https://www.gforcepowersports.com/inventory, https://www.gforcepowersports.com/inventory/ATV, https://www.gforcepowersports.com/inventory/boatflag, https://www.gforcepowersports.com/inventory/DIRT-BIKE and https://www.gforcepowersports.com/inventory/new-electric-vehicle all use the title “Inventory | G-Force Powersports”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://www.gforcepowersports.com/inventory/featured-new-vehicles, https://www.gforcepowersports.com/promotions, https://www.gforcepowersports.com/inventory/ATV, https://www.gforcepowersports.com/inventory/boatflag, https://www.gforcepowersports.com/inventory/DIRT-BIKE and https://www.gforcepowersports.com/inventory/new-electric-vehicle use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.gforcepowersports.com/inventory has no <h1> headline, so visitors and search engines get no clear main topic.
10 pages slow to respond
https://www.gforcepowersports.com/contact-us, https://www.gforcepowersports.com/location-directions, https://www.gforcepowersports.com/inventory/featured-new-vehicles, https://www.gforcepowersports.com/inventory, https://www.gforcepowersports.com/promotions and https://www.gforcepowersports.com/schedule-test-ride and 4 others 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.
5 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 12 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
161 small tap targets
161 of 328 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 “Failed to load resource: net::ERR_CONNECTION_RESET”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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
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.
About 5,433 words of copy
The homepage carries about 5,433 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT”.
12 calls to action
The homepage has 12 calls to action, for example “Quick Quote”, “Schedule a Test Ride” and “Order Parts”.
2 short forms
2 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 36 testimonial or review blocks and 38 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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 Clarity (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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
49 other companies contacted
Loading the homepage contacts 49 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 gforcepowersports.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
Company
- Headquarters
- Lakewood
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on gforcepowersports.com, including 27 speed issues and 3 SEO issues. 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.