Website review, no card needed

cloudacademy.com logo

cloudacademy.com website review

Visit site (opens in a new tab)Reviewed 29 October 202637 issues · 81 checks

This review found 37 issues worth fixing on cloudacademy.com, 15 of them high impact, across 81 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
5.1 s3.6 sMay 9Oct 244.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.2 s
May 16, 20263.9 s
May 23, 20263.8 s
May 30, 20263.9 s
Jun 6, 20264.1 s
Jun 13, 20264.2 s
Jun 20, 20264.6 s
Jun 27, 20264.6 s
Jul 4, 20264.7 s
Jul 11, 20264.8 s
Jul 18, 20264.5 s
Jul 25, 20264.5 s
Aug 1, 20264.7 s
Aug 8, 20264.7 s
Aug 15, 20264.7 s
Aug 22, 20264.9 s
Aug 29, 20264.8 s
Sep 5, 20264.8 s
Sep 12, 20264.8 s
Sep 19, 20264.7 s
Sep 26, 20264.7 s
Oct 3, 20264.7 s
Oct 10, 20264.7 s
Oct 17, 20264.6 s
Oct 24, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
349 ms209 msMay 9Oct 24289 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026237 ms
May 16, 2026225 ms
May 23, 2026227 ms
May 30, 2026253 ms
Jun 6, 2026256 ms
Jun 13, 2026262 ms
Jun 20, 2026292 ms
Jun 27, 2026279 ms
Jul 4, 2026304 ms
Jul 11, 2026311 ms
Jul 18, 2026296 ms
Jul 25, 2026308 ms
Aug 1, 2026324 ms
Aug 8, 2026309 ms
Aug 15, 2026314 ms
Aug 22, 2026333 ms
Aug 29, 2026288 ms
Sep 5, 2026280 ms
Sep 12, 2026262 ms
Sep 19, 2026245 ms
Sep 26, 2026251 ms
Oct 3, 2026261 ms
Oct 10, 2026278 ms
Oct 17, 2026286 ms
Oct 24, 2026289 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 cloudacademy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

cloudacademy.com does not allow embedding, so this is Google's rendering of the page.

Speed

9 to fix42
  • Reduce unused JavaScript

    6.3 s · 1,012 KiB

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

  • Mobile performance score: 42

    42/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, Google Tag Manager and Cookiebot and others), adding 1.4 MB and 1.1 s of main-thread time.

  • Render-blocking requests

    900 ms

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

  • Google CDN adds 583 ms

    583 ms

    Google CDN costs a phone 583 ms of main-thread work and 741 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.

  • Google Tag Manager adds 371 ms

    371 ms

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

  • 16 long tasks on the main thread

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

  • Main-thread work: 3.6 s

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

  • 2,224 HTML elements

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

  • Reduce unused CSS

    280 ms · 62 KiB

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

  • Legacy JavaScript

    150 ms · 23 KiB

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

  • Use efficient cache lifetimes

    100 ms · 37 KiB

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

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 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.

  • Real-user LCP: 4.8 s

    4.8 s

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

  • Real-user FCP: 4.0 s

    4.0 s

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

  • Real-user TTFB: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 14.8 s

    14.8 s

    Your largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your experience with personalised…”.

  • Time to Interactive: 16.4 s

    16.4 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Speed Index: 7.4 s

    7.4 s

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

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

    +24%

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

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

    +12%

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

4 checks passed
  • Real-user INP: 155 ms

    155 ms

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

  • First Contentful Paint: 0.8 s

    0.8 s

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 49 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 49 requests on a phone: scripts 2.0 MB (25), other files 402 KiB (13) and fonts 75 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.72 g

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

2 to fixGoogle 10097
  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

1 checks passed
  • 35 automated accessibility rules passed

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

SEO

9 to fixGoogle 6650
  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (20 characters)

    Your title is only 20 characters: “QA Learning Platform”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No canonical URL

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

  • Meta description is long (232 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("ca_logo.svg")”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://cloudacademy.com/sitemap.xml, so Google discovers your pages only by following links.

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

1 checks passed
  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

    There is no /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.

  • Organization data: 4 of 6 facts

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

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • 2 redirects before the homepage

    Opening https://cloudacademy.com goes through 2 redirects before the homepage loads.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (platform.qa.com).

  • Valid certificate (152 days left)

    The certificate from Amazon · Amazon RSA 2048 M01 verifies for cloudacademy.com and is valid for another 152 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://cloudacademy.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

Domain and trust

  • DNSSEC is off

    qa.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

3 checks passed
  • Domain is 32 years old

    32 years

    qa.com was registered in Oct 1994 through IONOS SE. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only letsencrypt.org, amazon.com and amazontrust.com to issue certificates for qa.com, so a mis-issued certificate from anyone else is refused.

  • Registered until Oct 2027

    qa.com is registered until Oct 2027.

Content and conversion

6 to fix25
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

  • Only about 3 words

    The homepage has only about 3 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Email authentication

85
  • Email authentication score: 85/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com include:sendgrid.net include:_spf.salesforce.com include:amazonses.com include:spf.maila…”.

  • DKIM signing found

    A DKIM key is published (selector “google”, “k1” and “s1”), so receivers can verify mail really came from you.

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 (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

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

  • 6 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

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

Upkeep, stack and company

Stack

Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on cloudacademy.com, including 18 speed issues, 9 SEO issues and 6 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