Website review, no card needed

maximausa.com logo

maximausa.com website review

Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 79 checks

This review found 33 issues worth fixing on maximausa.com, 4 of them high impact, across 79 checks. The most urgent: 7 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
960 ms806 msMay 23Nov 7930 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026869 ms
May 30, 2026860 ms
Jun 6, 2026874 ms
Jun 13, 2026894 ms
Jun 20, 2026934 ms
Jun 27, 2026918 ms
Jul 4, 2026914 ms
Jul 11, 2026934 ms
Jul 18, 2026916 ms
Jul 25, 2026932 ms
Aug 1, 2026942 ms
Aug 8, 2026924 ms
Aug 15, 2026909 ms
Aug 22, 2026890 ms
Aug 29, 2026902 ms
Sep 5, 2026908 ms
Sep 12, 2026910 ms
Sep 19, 2026914 ms
Sep 26, 2026889 ms
Oct 3, 2026854 ms
Oct 10, 2026840 ms
Oct 17, 2026824 ms
Oct 24, 2026830 ms
Oct 31, 2026878 ms
Nov 7, 2026930 ms
Real-visitor tap response (INP)75th percentile, phones
80 ms78 msMay 23Nov 779 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202678 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202678 ms
Aug 8, 202678 ms
Aug 15, 202679 ms
Aug 22, 202678 ms
Aug 29, 202678 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202680 ms
Sep 26, 202679 ms
Oct 3, 202679 ms
Oct 10, 202679 ms
Oct 17, 202678 ms
Oct 24, 202678 ms
Oct 31, 202678 ms
Nov 7, 202679 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

Full-page screenshot of maximausa.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maximausa.com at 0.5 s0.5 s
  2. maximausa.com at 0.9 s0.9 s
  3. maximausa.com at 1.4 s1.4 s
  4. maximausa.com at 1.8 s1.8 s
  5. maximausa.com at 2.3 s2.3 s
  6. maximausa.com at 2.7 s2.7 s
  7. maximausa.com at 3.2 s3.2 s
  8. maximausa.com at 3.6 s3.6 s

Speed

9 to fix95
  • Improve image delivery

    620 KiB

    12 images could be 620 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, OptiMonk and POWr and others), adding 1.4 MB and 440 ms of main-thread time.

  • Reduce unused JavaScript

    498 KiB

    About 498 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    450 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Use efficient cache lifetimes

    395 KiB

    11 files are served with short cache lifetimes, so returning visitors download them again (395 KiB).

  • Main-thread work: 2.1 s

    A phone's processor spends 2.1 s on main-thread work while loading, 847 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Klaviyo adds 137 ms

    137 ms

    Klaviyo costs a phone 137 ms of main-thread work and 312 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.

  • cloudfront.net adds 36 ms

    36 ms

    cloudfront.net costs a phone 36 ms of main-thread work and 370 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.

  • Shopify adds 29 ms

    29 ms

    Shopify costs a phone 29 ms of main-thread work and 333 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.

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 79 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    40 KiB

    Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    25 KiB

    25 KiB could be saved by minifying JavaScript.

  • 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.

2 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix100
  • Time to Interactive: 13.1 s

    13.1 s

    The page becomes fully interactive after 13.1 s. Good is under 3.8 s.

  • Largest Contentful Paint: 2.8 s

    2.8 s

    Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 78 ms to 79 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-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

10 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.0 s

    1.0 s

    Real visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 78 ms

    78 ms

    Real visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 530 ms

    530 ms

    Real visitors wait 530 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 43 ms

    43 ms

    Scripts block the page for only 43 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix81
  • Page weight: 3.3 MB in 265 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 265 requests on a phone: scripts 1.5 MB (93), images 863 KiB (14) and other files 833 KiB (129). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    26BI_BIKE_Homepage-Banner_May_2048X650_e8fb062b-2af3-4395-98 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).

  • About 0.9 g of CO₂ per visit

    0.95 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 113.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9496
  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (8 elements)

    Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10086
  • Meta description is long (318 characters)

    Your meta description is 318 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • One H1 headline

    Your <h1> is empty.

  • 128 internal links, 10 external

    The homepage links to 128 pages on maximausa.com and 10 external pages.

5 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “Maxima Racing Oils – MaximaUsa”.

  • Canonical URL set

    The canonical URL is https://maximausa.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://maximausa.com/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (467 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://maximausa.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix76
  • 4 pages share 2 titles

    https://maximausa.com/collections/trans-gear-oil and https://maximausa.com/collections/auto-trans-gear-oil all use the title “TRANS/GEAR OIL – MaximaUsa”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://maximausa.com/collections/performance-auto has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://maximausa.com/collections/2-stroke-oil/2-STROKE-OIL and https://maximausa.com/collections/performance-auto-2-stroke 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 https://maximausa.com/collections/2-stroke-oil/2-STROKE-OIL, whose canonical is https://maximausa.com/collections/2-stroke-oil/2-stroke-oil. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://maximausa.com/collections/powersports, https://maximausa.com/collections/aerosol, https://maximausa.com/collections/2-stroke-oil/2-STROKE-OIL, https://maximausa.com/collections/4-stroke-oils, https://maximausa.com/collections/sxs-oil-change-kits-1 and https://maximausa.com/collections/oil-change-kits and 9 others have 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 62 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    39 of 44 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 165 words

    The homepage has only about 165 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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.

2 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “SHOP ALL POWERSPORTS”, “SHOP ALL PERFORMANCE AUTO” and “SHOP ALL BIKE”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 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.

  • 38 other companies contacted

    Loading the homepage contacts 38 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 maximausa.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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Hulk Form Builder · Minmaxify Order Limits · Optimonk Popup Cro A B Test · Klaviyo Email Marketing Sms · Free Shipping Popup · Forms · govedia.com · appspot.com · powr.io · roseperl.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
Bootstrap
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Santee

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on maximausa.com, including 11 speed issues, 4 SEO issues and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25