Website review, no card needed

cognita.com logo

cognita.com website review

Visit site (opens in a new tab)Reviewed 20 November 202644 issues · 97 checks

This review found 44 issues worth fixing on cognita.com, 16 of them high impact, across 97 checks. The most urgent: render-blocking requests. 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.8 s2.4 sMay 30Nov 142.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Nov 7, 20262.6 s
Nov 14, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
182 ms148 msMay 30Nov 14178 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026152 ms
Jun 6, 2026152 ms
Jun 13, 2026158 ms
Jun 20, 2026158 ms
Jun 27, 2026158 ms
Jul 4, 2026160 ms
Jul 11, 2026155 ms
Jul 18, 2026156 ms
Jul 25, 2026158 ms
Aug 1, 2026158 ms
Aug 8, 2026163 ms
Aug 15, 2026162 ms
Aug 22, 2026160 ms
Aug 29, 2026163 ms
Sep 5, 2026165 ms
Sep 12, 2026170 ms
Sep 19, 2026176 ms
Sep 26, 2026174 ms
Oct 3, 2026175 ms
Oct 10, 2026174 ms
Oct 17, 2026174 ms
Oct 24, 2026177 ms
Oct 31, 2026174 ms
Nov 7, 2026173 ms
Nov 14, 2026178 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 cognita.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

13 to fix40
  • Render-blocking requests

    2.0 s

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

  • Mobile performance score: 40

    40/100

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

  • Main-thread work: 5.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Vimeo and Cookiebot and others), adding 13.1 MB and 1.5 s of main-thread time.

  • Use efficient cache lifetimes

    900 ms · 1.4 MB

    105 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

  • Vimeo adds 426 ms

    426 ms

    Vimeo costs a phone 426 ms of main-thread work and 11.4 MB 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

    300 ms · 948 KiB

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

  • Reduce unused CSS

    750 ms · 169 KiB

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

  • Google Tag Manager adds 535 ms

    535 ms

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

  • Improve image delivery

    150 ms · 400 KiB

    6 images could be 400 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.

  • Cookiebot adds 286 ms

    286 ms

    Cookiebot costs a phone 286 ms of main-thread work and 166 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 Maps adds 197 ms

    197 ms

    Google Maps costs a phone 197 ms of main-thread work and 787 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,026 HTML elements

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

  • 19 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Minify JavaScript

    30 KiB

    30 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    27 KiB

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

  • Minify CSS

    18 KiB

    18 KiB could be saved by minifying CSS.

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

    42 ms

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

Core Web Vitals

11 to fix33
  • 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: 35.3 s

    35.3 s

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

  • Largest Contentful Paint: 9.2 s

    9.2 s

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

  • Speed Index: 12.7 s

    12.7 s

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

  • Total Blocking Time: 904 ms

    904 ms

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

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Real-user INP: 202 ms

    202 ms

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 15 images without width and height

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

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

    +15%

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

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.7 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

2 to fix69
  • Page weight: 18.1 MB in 166 requests

    18.1 MB

    Your homepage downloads 18.1 MB in 166 requests on a phone: other files 10.6 MB (41), images 3.9 MB (41) and scripts 2.9 MB (57). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    cognita-logo.png 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).

  • 1 image below the first screen load straight away

    1 image further down the page (70 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.1 g of CO₂ per visit

    5.13 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8488
  • 16 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails 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 (48 elements)

    All page content should be contained by landmarks: 48 elements on the page fail 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 link without text

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

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

5 to fixGoogle 8577
  • No H1 headline

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

  • Title is short (22 characters)

    Your title is only 22 characters: “Home - Cognita Schools”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 3 links with vague text

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 92 internal links, 27 external

    The homepage links to 92 pages on cognita.com and 27 external pages.

5 checks passed
  • Meta description: 111 characters

    Your meta description is 111 characters: “Discover Cognita, a global system of schools helping students and educators thrive in a rapidly evolving world.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.cognita.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.cognita.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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 11 pages without a meta description

    https://www.cognita.com/news-and-views, https://www.cognita.com/holistic-education, https://www.cognita.com/holistic-education/academic-excellence, https://www.cognita.com/holistic-education/wellbeing, https://www.cognita.com/holistic-education/digital-learning and https://www.cognita.com/holistic-education/global-and-social-action and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 31 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.

  • 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 5894
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

    The homepage carries about 2,120 words of visible text.

7 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 12 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 4 of them by other companies (measured from a US location before any click).

  • 17 other companies contacted

    Loading the homepage contacts 17 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.

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 cognita.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Akamai

Company

Founded
2004
Headquarters
Milton Keynes

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on cognita.com, including 24 speed issues, 5 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