Website review, no card needed

akamaibasics.com logo

akamaibasics.com website review

Visit site (opens in a new tab)Reviewed 19 October 202632 issues · 77 checks

This review found 32 issues worth fixing on akamaibasics.com, 10 of them high impact, across 77 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
1.8 s1.3 sMay 2Oct 171.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
148 ms98 msMay 2Oct 17139 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026112 ms
May 9, 2026112 ms
May 16, 2026110 ms
May 23, 2026105 ms
May 30, 2026105 ms
Jun 6, 2026105 ms
Jun 13, 2026104 ms
Jun 20, 2026105 ms
Jun 27, 2026113 ms
Jul 4, 2026113 ms
Jul 11, 2026114 ms
Jul 18, 2026113 ms
Jul 25, 2026113 ms
Aug 1, 2026114 ms
Aug 8, 2026118 ms
Aug 15, 2026120 ms
Aug 22, 2026119 ms
Aug 29, 2026122 ms
Sep 5, 2026127 ms
Sep 12, 2026129 ms
Sep 19, 2026137 ms
Sep 26, 2026142 ms
Oct 3, 2026140 ms
Oct 10, 2026138 ms
Oct 17, 2026139 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 akamaibasics.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. akamaibasics.com at 1.0 s1.0 s
  2. akamaibasics.com at 2.0 s2.0 s
  3. akamaibasics.com at 3.0 s3.0 s
  4. akamaibasics.com at 4.0 s4.0 s
  5. akamaibasics.com at 5.0 s5.0 s
  6. akamaibasics.com at 6.0 s6.0 s
  7. akamaibasics.com at 7.0 s7.0 s
  8. akamaibasics.com at 8.0 s8.0 s

Speed

11 to fix39
  • Reduce unused JavaScript

    1.2 s · 316 KiB

    About 316 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Main-thread work: 10.0 s

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

  • Mobile performance score: 39

    39/100

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

  • 3,721 HTML elements

    The page has 3,721 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 (govx.com, Shopify and Klaviyo and others), adding 954 KiB and 1.7 s of main-thread time.

  • govx.com adds 854 ms

    854 ms

    govx.com costs a phone 854 ms of main-thread work and 7 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.

  • Use efficient cache lifetimes

    700 ms · 131 KiB

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

  • Reduce unused CSS

    600 ms · 49 KiB

    About 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 17 long tasks on the main thread

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

  • Render-blocking requests

    350 ms

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

  • Klaviyo adds 172 ms

    172 ms

    Klaviyo costs a phone 172 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.

  • Improve image delivery

    232 KiB

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

  • Legacy JavaScript

    150 ms · 18 KiB

    Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Duplicated JavaScript

    100 ms · 29 KiB

    29 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

  • 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: 21 ms

    21 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Akamai Basics natural oral care products, including a miner…”.

  • Time to Interactive: 19.1 s

    19.1 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Tap response (INP) got 24% slower for real visitors

    +24%

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

  • Real-user TTFB: 905 ms

    905 ms

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

4 checks passed
  • Real-user INP: 147 ms

    147 ms

    Real visitors wait 147 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: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

3 to fix69
  • Page weight: 3.3 MB in 222 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 222 requests on a phone: images 1.1 MB (36), scripts 1.1 MB (102) and other files 819 KiB (68). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    basics-mobile-v3.jpg 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).

  • 2 images far larger than shown

    104 KiB

    2 images are downloaded at several times the size a phone draws them, for example mineral-toothpowder-mockup_30ae5a5f-62ba-4233-b367-71b8a26b3 at 2,509 px wide, shown at 350 px. Resized copies would save about 104 KiB.

  • About 0.9 g of CO₂ per visit

    0.94 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.94 g of CO₂e: 113.0 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

1 to fixGoogle 10099
  • All page content should be contained by landmarks (18 elements)

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

2 checks passed
  • Every image has alt text

    All 99 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Meta description is long (194 characters)

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 244 internal links, 15 external

    The homepage links to 244 pages on akamaibasics.com and 15 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Natural oral care and body care essentials”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Akamai - Truly Natural Oral Care and Body Care Essentials”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: OnlineStore, Organization 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://akamaibasics.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://akamaibasics.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://akamaibasics.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://akamaibasics.com/pages/bulk-buying, https://akamaibasics.com/customer_authentication/redirect and https://akamaibasics.com/pages/help-center have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://akamaibasics.com/customer_authentication/redirect, https://akamaibasics.com/pages/help-center, https://akamaibasics.com/products/akamai-oral-care-complete-kit, https://akamaibasics.com/products/oral-care-essentials-kit, https://akamaibasics.com/products/remineralizing-toothpaste-powder and https://akamaibasics.com/products/essential-oil-free-mineral-toothpowder and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://akamaibasics.com/products/oral-care-essentials-kit and https://akamaibasics.com/products/essential-oil-free-mineral-toothpowder have 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 76 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.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'dataset') https://akamaibasics.com/cdn/shop/t/186/assets/flexible-area.js?v=17…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 2,269 words of copy

    The homepage carries about 2,269 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW ORAL CARE ESSENTIALS KIT” and “SHOP NOW CORE ESSENTIALS KIT”.

  • 28 calls to action

    The homepage has 28 calls to action, for example “Shop”, “Shop All” and “Shop Now Oral Care Essentials Kit”.

  • 7 short forms

    7 short forms (0 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 159 testimonial or review blocks, a star rating and “95,000+ CUSTOMERS”.

  • Analytics in place

    Analytics detected: Hotjar.

  • 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

1 to fix
  • 7 trackers load before any consent

    7

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

  • 22 cookies set on arrival

    22

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

  • 51 other companies contacted

    Loading the homepage contacts 51 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 akamaibasics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on akamaibasics.com, including 20 speed issues and 2 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

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