Website review, no card needed

ascentprotein.com logo

ascentprotein.com website review

Visit site (opens in a new tab)Reviewed 4 November 202639 issues · 92 checks

This review found 39 issues worth fixing on ascentprotein.com, 11 of them high impact, across 92 checks. The most urgent: fails Core Web Vitals for real visitors. 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
2.5 s2.2 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
102 ms93 msMay 16Oct 3195 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202694 ms
May 23, 202694 ms
May 30, 202694 ms
Jun 6, 202696 ms
Jun 13, 202696 ms
Jun 20, 202696 ms
Jun 27, 202697 ms
Jul 4, 202699 ms
Jul 11, 2026101 ms
Jul 18, 202698 ms
Jul 25, 202698 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202696 ms
Aug 22, 202696 ms
Aug 29, 202696 ms
Sep 5, 202695 ms
Sep 12, 202695 ms
Sep 19, 202695 ms
Sep 26, 202694 ms
Oct 3, 202694 ms
Oct 10, 202694 ms
Oct 17, 202695 ms
Oct 24, 202695 ms
Oct 31, 202695 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 ascentprotein.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ascentprotein.com at 0.9 s0.9 s
  2. ascentprotein.com at 1.8 s1.8 s
  3. ascentprotein.com at 2.8 s2.8 s
  4. ascentprotein.com at 3.7 s3.7 s
  5. ascentprotein.com at 4.6 s4.6 s
  6. ascentprotein.com at 5.5 s5.5 s
  7. ascentprotein.com at 6.5 s6.5 s
  8. ascentprotein.com at 7.4 s7.4 s

Speed

11 to fix50
  • Main-thread work: 6.8 s

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

  • Reduce unused JavaScript

    650 ms · 768 KiB

    About 768 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 650 ms faster on a phone.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (rebuyengine.com, Shopify and Klaviyo and others), adding 1.9 MB and 712 ms of main-thread time.

  • Render-blocking requests

    750 ms

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

  • Reduce unused CSS

    300 ms · 128 KiB

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

  • Improve image delivery

    383 KiB

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

  • rebuyengine.com adds 269 ms

    269 ms

    rebuyengine.com costs a phone 269 ms of main-thread work and 801 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.

  • 2,009 HTML elements

    The page has 2,009 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Shopify adds 118 ms

    118 ms

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

  • LoyaltyLion adds 52 ms

    52 ms

    LoyaltyLion costs a phone 52 ms of main-thread work and 361 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

    150 ms · 148 KiB

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

  • 18 long tasks on the main thread

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

  • Legacy JavaScript

    58 KiB

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

  • Font display

    50 ms

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

  • Minify JavaScript

    15 KiB

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

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

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

  • Time to Interactive: 23.2 s

    23.2 s

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

  • Largest Contentful Paint: 8.0 s

    8.0 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 862 ms

    862 ms

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

  • Total Blocking Time: 566 ms

    566 ms

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 7 images without width and height

    7 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 94 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -6%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 83 ms

    83 ms

    Real visitors wait 83 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.7 MB in 334 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 334 requests on a phone: scripts 2.0 MB (143), images 1.1 MB (27) and other files 1.0 MB (120). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (139 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 1.3 g of CO₂ per visit

    1.34 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

7 to fixGoogle 8291
  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    4 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Links must have discernible text (5 elements)

    Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 12 tap targets too small

    12 tap targets are too small or too close together to hit reliably with a finger.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 143 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 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9286
  • Title is short (21 characters)

    Your title is only 21 characters: “Home | Ascent Protein”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (186 characters)

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

  • 6 links with vague text

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

  • 93 internal links, 26 external

    The homepage links to 93 pages on ascentprotein.com and 26 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Advanced Collagen Peptides”.

  • Canonical URL set

    The canonical URL is https://www.ascentprotein.com/.

  • Structured data in place

    Structured data found: LocalBusiness and OnlineStore.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.ascentprotein.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.

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.

  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    9 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 9 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 9 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7770
  • 1 broken image

    1 image failed to load on a phone, for example https://www.ascentprotein.com/.

  • 20 small tap targets

    20 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,300 words of copy

    The homepage carries about 1,300 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop” and “SHOP NOW”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop”, “Learn More” and “Apply”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 19 testimonial or review blocks, a star rating and 2 trust badges.

  • 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

1 to fix
  • 2 trackers load before any consent

    2

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

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 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 ascentprotein.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 22 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Seowill Redirects · Triplewhale · Klaviyo Email Marketing Sms · Seowill Sticky Cart · Rebuy Personalization Engine · Xo Insert Code · Hulk Form Builder · Simprosys Google Shopping Feed · Gdpr Backpack · Navidium Shipping Protection · azureedge.net · stamped.io · gorgias.chat · dailykarma.io · rechargecdn.com · rebuyengine.com · cloudfront.net · nofraud.com · govx.com · 9gtb.com · useamp.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
jQuery
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Denver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on ascentprotein.com, including 20 speed issues, 3 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