Website review, no card needed

Absolute Web logo

absoluteweb.com website review

Visit site (opens in a new tab)Reviewed 21 October 202651 issues · 76 checks

This review found 51 issues worth fixing on absoluteweb.com, 23 of them high impact, across 76 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Absolute Web

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

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

Site score

67D

Not ranked: the homepage didn't load normally in this review.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. absoluteweb.com at 1.5 s1.5 s
  2. absoluteweb.com at 3.0 s3.0 s
  3. absoluteweb.com at 4.6 s4.6 s
  4. absoluteweb.com at 6.1 s6.1 s
  5. absoluteweb.com at 7.6 s7.6 s
  6. absoluteweb.com at 9.1 s9.1 s
  7. absoluteweb.com at 10.6 s10.6 s
  8. absoluteweb.com at 12.1 s12.1 s

Speed

12 to fix33
  • Improve image delivery

    2.1 s · 4.0 MB

    28 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Main-thread work: 35.1 s

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

  • Clarity adds 2.3 s

    2.3 s

    Clarity costs a phone 2.3 s of main-thread work and 29 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.6 s

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

  • Reduce unused CSS

    1.1 s · 167 KiB

    About 167 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: 33

    33/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Google Tag Manager and elfsight.com and others), adding 1.1 MB and 4.1 s of main-thread time.

  • Google Tag Manager adds 967 ms

    967 ms

    Google Tag Manager costs a phone 967 ms of main-thread work and 673 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.

  • Reduce unused JavaScript

    956 KiB

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

  • Use efficient cache lifetimes

    150 ms · 410 KiB

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

  • 20 long tasks on the main thread

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

  • 2,448 HTML elements

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    55 KiB

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

  • Duplicated JavaScript

    45 KiB

    45 KiB JavaScript is shipped twice across bundles.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

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

  • Largest Contentful Paint: 18.6 s

    18.6 s

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

  • Time to Interactive: 43.1 s

    43.1 s

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

  • Speed Index: 15.2 s

    15.2 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • 22 images without width and height

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

2 checks passed
  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (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

5 to fix18
  • Page weight: 33.9 MB in 543 requests

    33.9 MB

    Your homepage downloads 33.9 MB in 543 requests on a phone: media 24.1 MB (2), images 7.1 MB (84) and scripts 2.2 MB (140). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    absolute-web-meeting.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

  • 14 images far larger than shown

    1.8 MB

    14 images are downloaded at several times the size a phone draws them, for example absolute-web-meeting.png at 1,200 px wide, shown at 340 px. Resized copies would save about 1.8 MB.

  • 21 images in older formats

    21 images (4.7 MB) 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.

  • 14 images below the first screen load straight away

    14 images further down the page (4.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 9.6 g of CO₂ per visit

    9.61 g

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

Accessibility

6 to fixGoogle 9191
  • 3 tap targets too small

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails 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.

  • 5 form fields without a label

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

1 checks passed
  • 39 automated accessibility rules passed

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

10 to fixGoogle 9239
  • Page is set to noindex

    The robots meta tag says “noindex,nofollow”: Google is told not to list this page at all.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (16 characters)

    Your title is only 16 characters: “Just a moment...”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 20 links with vague text

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

2 checks passed
  • 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://absoluteweb.com/sitemap_index.xml.

AI search readiness

100
1 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.

Best practices

3 to fixGoogle 8885
  • 12 small tap targets

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

  • 2 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • Homepage answers HTTP 403

    Your homepage answered with HTTP 403, so visitors and search engines may see an error page.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

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

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get in touch”.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 11 cookies set on arrival

    11

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

  • 32 other companies contacted

    Loading the homepage contacts 32 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 absoluteweb.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 51 issues on absoluteweb.com, including 21 speed issues, 10 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