Website review, no card needed

ascentialedge.com logo

ascentialedge.com website review

Visit site (opens in a new tab)Reviewed 1 November 202635 issues · 81 checks

This review found 35 issues worth fixing on ascentialedge.com, 9 of them high impact, across 81 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
4.6 s1.9 sMay 9Oct 244.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.7 s
May 16, 20262.9 s
May 23, 20262.7 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.7 s
Jul 18, 20263.0 s
Jul 25, 20263.7 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20263.8 s
Aug 22, 20264.0 s
Aug 29, 20264.1 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.3 s
Sep 26, 20264.3 s
Oct 3, 20264.1 s
Oct 10, 20264.0 s
Oct 17, 20263.9 s
Oct 24, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
153 ms91 msMay 9Oct 24132 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202698 ms
May 16, 2026104 ms
May 23, 2026107 ms
May 30, 2026113 ms
Jun 6, 2026109 ms
Jun 13, 2026112 ms
Jun 20, 2026119 ms
Jun 27, 2026121 ms
Jul 4, 2026127 ms
Jul 11, 2026126 ms
Jul 18, 2026138 ms
Jul 25, 2026139 ms
Aug 1, 2026139 ms
Aug 8, 2026146 ms
Aug 15, 2026137 ms
Aug 22, 2026137 ms
Aug 29, 2026136 ms
Sep 5, 2026130 ms
Sep 12, 2026127 ms
Sep 19, 2026124 ms
Sep 26, 2026121 ms
Oct 3, 2026123 ms
Oct 10, 2026127 ms
Oct 17, 2026127 ms
Oct 24, 2026132 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 ascentialedge.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ascentialedge.com at 0.4 s0.4 s
  2. ascentialedge.com at 0.8 s0.8 s
  3. ascentialedge.com at 1.3 s1.3 s
  4. ascentialedge.com at 1.7 s1.7 s
  5. ascentialedge.com at 2.1 s2.1 s
  6. ascentialedge.com at 2.5 s2.5 s
  7. ascentialedge.com at 2.9 s2.9 s
  8. ascentialedge.com at 3.4 s3.4 s

Speed

6 to fix61
  • Mobile performance score: 61

    61/100

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

  • Reduce unused JavaScript

    450 ms · 290 KiB

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

  • Improve image delivery

    150 ms · 376 KiB

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

  • Render-blocking requests

    450 ms

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

  • 6 long tasks on the main thread

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

  • ctfassets.net adds 0 ms

    0 ms

    ctfassets.net costs a phone 0 ms of main-thread work and 394 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 · 125 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Optanon, weglot.com and SalesLoft and others), adding 941 KiB and 124 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 21 KiB

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    33 KiB

    About 33 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 620 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.7 s

    5.7 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Superior outcomes, industry leading technology”.

  • Time to Interactive: 10.3 s

    10.3 s

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

  • Speed Index: 6.3 s

    6.3 s

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

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

    +28%

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

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

    +41%

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

  • Total Blocking Time: 269 ms

    269 ms

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

  • Cumulative Layout Shift: 0.115

    0.115

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

3 checks passed
  • Real-user INP: 161 ms

    161 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

Images and page weight

3 to fix81
  • An image on the first screen is lazy-loaded

    image 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).

  • 4 images far larger than shown

    336 KiB

    4 images are downloaded at several times the size a phone draws them, for example epsilon.png at 1,200 px wide, shown at 140 px. Resized copies would save about 336 KiB.

  • 4 images below the first screen load straight away

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

  • 4 images in older formats

    4 images (363 KiB) are 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 0.5 g of CO₂ per visit

    0.51 g

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

1 checks passed
  • Page weight: 1.8 MB in 84 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 84 requests on a phone: scripts 768 KiB (29), images 564 KiB (28) and fonts 390 KiB (5). That is a lean page.

Accessibility

7 to fixGoogle 9793
  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 49 links without text

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

  • 1 form field without a label

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 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

2 to fixGoogle 9294
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

  • 125 internal links, 6 external

    The homepage links to 125 pages on ascentialedge.com and 6 external pages.

7 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Grow faster, smarter, and more efficiently with Flywheel's suite of digital commerce solutions, purpose-built for the w…”.

  • One H1 headline

    Your main headline reads: “Grow faster, smarter, and more efficiently with Flywheel”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Flywheel | Driving growth in digital commerce”.

  • Canonical URL set

    The canonical URL is https://www.flywheeldigital.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://www.flywheeldigital.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.

  • No llms.txt

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

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

Other pages

1 to fix93
  • 4 linked pages hidden from search

    https://www.flywheeldigital.com/insights, https://www.flywheeldigital.com/blog, https://www.flywheeldigital.com/guides and https://www.flywheeldigital.com/webinars are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 15 internal pages checked

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

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

  • Every page has a meta description

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 50 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://use.typekit.net/arv2wus.css' violates the following Content Security Policy directive: "connect-…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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 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 573 words of copy

    The homepage carries about 573 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Learn More”, “Contact Us” and “Subscribe”.

  • 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: 9 customer or partner logos and “4.5k clients”.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 ascentialedge.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
Next.js
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on ascentialedge.com, including 17 speed issues, 2 SEO issues and 2 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