Website review, no card needed

akathletics.com logo

akathletics.com website review

Visit site (opens in a new tab)Reviewed 21 October 202641 issues · 89 checks

This review found 41 issues worth fixing on akathletics.com, 12 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
5.0 s627 msMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.5 s
May 16, 20264.4 s
May 23, 20264.4 s
May 30, 20264.3 s
Jun 6, 20263.1 s
Jun 13, 20262.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
311 ms58 msMay 2Oct 1788 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026261 ms
May 9, 2026282 ms
May 16, 2026281 ms
May 23, 2026282 ms
May 30, 2026271 ms
Jun 6, 2026135 ms
Jun 13, 2026110 ms
Jun 20, 202696 ms
Jun 27, 202696 ms
Jul 4, 202691 ms
Jul 11, 202694 ms
Jul 18, 202691 ms
Jul 25, 202691 ms
Aug 1, 202690 ms
Aug 8, 202687 ms
Aug 15, 202687 ms
Aug 22, 202688 ms
Aug 29, 202689 ms
Sep 5, 202689 ms
Sep 12, 202695 ms
Sep 19, 202693 ms
Sep 26, 202689 ms
Oct 3, 202695 ms
Oct 10, 202687 ms
Oct 17, 202688 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 akathletics.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. akathletics.com at 0.4 s0.4 s
  2. akathletics.com at 0.8 s0.8 s
  3. akathletics.com at 1.1 s1.1 s
  4. akathletics.com at 1.5 s1.5 s
  5. akathletics.com at 1.9 s1.9 s
  6. akathletics.com at 2.3 s2.3 s
  7. akathletics.com at 2.6 s2.6 s
  8. akathletics.com at 3.0 s3.0 s

Speed

12 to fix37
  • Reduce unused JavaScript

    8.9 s · 2.3 MB

    About 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.9 s faster on a phone.

  • Use efficient cache lifetimes

    1.6 s · 1.1 MB

    25 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Render-blocking requests

    2.4 s

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

  • Reduce unused CSS

    1.1 s · 189 KiB

    About 189 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: 37

    37/100

    Your mobile performance score is 37 (desktop: 66). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.5 s

    A phone's processor spends 4.5 s on main-thread work while loading, 2.6 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 (YouTube, chatra.io and route.com and others), adding 3.4 MB and 1.6 s of main-thread time.

  • Improve image delivery

    550 ms · 646 KiB

    16 images could be 646 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

  • YouTube adds 757 ms

    757 ms

    YouTube costs a phone 757 ms of main-thread work and 1.9 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.

  • chatra.io adds 306 ms

    306 ms

    chatra.io costs a phone 306 ms of main-thread work and 324 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.

  • route.com adds 227 ms

    227 ms

    route.com costs a phone 227 ms of main-thread work and 565 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.

  • 12 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    27 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 66 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • Minify JavaScript

    6 KiB

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

7 to fix100
  • First Contentful Paint: 14.5 s

    14.5 s

    The first text or image appears after 14.5 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 23.2 s

    23.2 s

    Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Submit a PO Form”.

  • Time to Interactive: 39.2 s

    39.2 s

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

  • Speed Index: 14.5 s

    14.5 s

    Visually, the page fills in at 14.5 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 442 ms

    442 ms

    Scripts block taps and scrolling for 442 ms in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.171

    0.171

    The layout shifts by 0.171 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 17 images without width and height

    17 images have no width and height attributes, so the layout jumps as each one loads.

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.6 s

    1.6 s

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

  • Real-user INP: 87 ms

    87 ms

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

  • Real-user CLS: 0.09

    0.09

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 514 ms

    514 ms

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

  • Tap response (INP) got 68% faster for real visitors

    -68%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 261 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 74% faster for real visitors

    -74%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.2 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

3 to fix53
  • Page weight: 6.6 MB in 344 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 344 requests on a phone: scripts 4.0 MB (93), other files 1,016 KiB (193) and images 852 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 15 images below the first screen load straight away

    15 images further down the page (757 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 7 images far larger than shown

    239 KiB

    7 images are downloaded at several times the size a phone draws them, for example outdoor-stadium-padding-category-long-button_1600x480.jpg at 1,600 px wide, shown at 350 px. Resized copies would save about 239 KiB.

  • About 1.9 g of CO₂ per visit

    1.86 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

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

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

    All page content should be contained by landmarks: 34 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Wrestling Mats, Wall Pads, Martial Arts Mats by AK Athletic Equipment”.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 64 internal links, 4 external

    The homepage links to 64 pages on akathletics.com and 4 external pages.

5 checks passed
  • Meta description: 81 characters

    Your meta description is 81 characters: “Buy gymnastics mats, martial arts mats, wrestling mats and wall padding directly.”.

  • Canonical URL set

    The canonical URL is https://akathletics.com/.

  • 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://akathletics.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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 (221 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://akathletics.com/collections/all and https://akathletics.com/collections/pole-pads-and-column-pads have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://akathletics.com/pages/government-purchase-order, whose canonical is https://akathletics.com/pages/purchase-order. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page with very little text

    https://akathletics.com/pages/government-purchase-order has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

3 to fixGoogle 5488
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Unexpected token ','”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • Only about 158 words

    The homepage has only about 158 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.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request a Quote”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop ∨”, “Request a Quote” and “Contact Us”.

  • 2 short forms

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 17 cookies set on arrival

    17

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

  • 48 other companies contacted

    Loading the homepage contacts 48 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 akathletics.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 41 issues on akathletics.com, including 19 speed issues, 4 SEO issues and 3 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