Website review, no card needed

carbon60.com logo

carbon60.com website review

Visit site (opens in a new tab)Reviewed 21 October 202627 issues · 73 checks

This review found 27 issues worth fixing on carbon60.com, 10 of them high impact, across 73 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
4.4 s2.6 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.2 s
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.1 s
Jun 6, 20262.8 s
Jun 13, 20263.0 s
Jun 20, 20263.3 s
Jun 27, 20263.4 s
Jul 4, 20264.0 s
Jul 11, 20264.2 s
Jul 18, 20264.1 s
Jul 25, 20263.5 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20263.4 s
Aug 22, 20263.3 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20262.9 s
Sep 19, 20263.1 s
Sep 26, 20263.0 s
Oct 3, 20263.2 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s

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 carbon60.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix34
  • Reduce unused JavaScript

    2.5 s · 672 KiB

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

  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 960 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.

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34 (desktop: 80). 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 (Google Tag Manager, Hubspot and Hotjar and others), adding 1.4 MB and 1.8 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 144 KiB

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

  • 15 long tasks on the main thread

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

  • Improve image delivery

    394 KiB

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

  • Main-thread work: 3.9 s

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

  • Legacy JavaScript

    150 ms · 27 KiB

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Phones get a much slower page than desktops

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

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

    4 ms

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

Core Web Vitals

10 to fix50
  • 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: 15.0 s

    15.0 s

    Your largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Unlock the Endless Power of Hybrid & Sovereign Cloud”.

  • Time to Interactive: 16.7 s

    16.7 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

    The first text or image appears after 5.3 s on a phone. Good is under 1.8 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.

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

2 checks passed
  • 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: 12.4 MB in 92 requests

    12.4 MB

    Your homepage downloads 12.4 MB in 92 requests on a phone: media 10.0 MB (2), scripts 1.7 MB (33) and images 546 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 3.5 g of CO₂ per visit

    3.52 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

3 to fix89
  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

SEO

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

  • 49 internal links, 2 external

    The homepage links to 49 pages on carbon60.com and 2 external pages.

8 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Unlock the endless power of hybrid and sovereign cloud with Carbon60. Managed cloud solutions, sovereign infrastructure…”.

  • One H1 headline

    Your main headline reads: “Unlock the Endless Power ofHybrid & Sovereign Cloud”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Carbon60 | Managed Cloud & Hybrid Infrastructure”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.carbon60.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,115 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 26 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 9687
  • 4 small tap targets

    4 of 10 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 “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • A 9-field form

    Your longest form asks for 9 fields (6 required). Every extra field lowers completion.

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

    The homepage carries about 1,122 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: “Learn more →” and “Contact Us Contact Us”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Learn more→”, “Contact UsContact Us” and “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks and 8 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

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

  • 27 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 carbon60.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
Analytics
Google Tag Manager
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on carbon60.com, including 18 speed issues, 1 SEO issue 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