Website review, no card needed

saintkentigern.com logo

saintkentigern.com website review

Visit site (opens in a new tab)Reviewed 28 October 202641 issues · 89 checks

This review found 41 issues worth fixing on saintkentigern.com, 12 of them high impact, across 89 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.5 s2.0 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.1 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
99 ms83 msMay 9Oct 2490 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202696 ms
May 16, 202697 ms
May 23, 202696 ms
May 30, 202695 ms
Jun 6, 202695 ms
Jun 13, 202693 ms
Jun 20, 202690 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202686 ms
Jul 18, 202685 ms
Jul 25, 202685 ms
Aug 1, 202686 ms
Aug 8, 202687 ms
Aug 15, 202689 ms
Aug 22, 202691 ms
Aug 29, 202694 ms
Sep 5, 202692 ms
Sep 12, 202690 ms
Sep 19, 202690 ms
Sep 26, 202690 ms
Oct 3, 202693 ms
Oct 10, 202694 ms
Oct 17, 202694 ms
Oct 24, 202690 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 saintkentigern.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix57
  • Render-blocking requests

    1.7 s

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

  • Improve image delivery

    300 ms · 1.3 MB

    13 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Reduce unused JavaScript

    900 ms · 686 KiB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Cookiebot and Other Google APIs/SDKs and others), adding 1.3 MB and 598 ms of main-thread time.

  • Use efficient cache lifetimes

    300 ms · 299 KiB

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

  • YouTube adds 398 ms

    398 ms

    YouTube costs a phone 398 ms of main-thread work and 1.1 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.

  • 2,345 HTML elements

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

  • Reduce unused CSS

    150 ms · 153 KiB

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

  • 7 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 89 but mobile only 57. 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.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

8 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: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Choose to believe”.

  • Time to Interactive: 20.3 s

    20.3 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 103 ms

    103 ms

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

  • Total Blocking Time: 197 ms

    197 ms

    Scripts block the page for only 197 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix68
  • Page weight: 3.7 MB in 72 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 72 requests on a phone: images 2.1 MB (34), scripts 1.2 MB (17) and fonts 138 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 13 images below the first screen load straight away

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

  • 8 images far larger than shown

    434 KiB

    8 images are downloaded at several times the size a phone draws them, for example eyJidWNrZXQiOiJkaWdpc3Rvcm0td2Vic2l0ZXMiLCJrZXkiOiJza28tbnot at 1,600 px wide, shown at 440 px. Resized copies would save about 434 KiB.

  • 2 images in older formats

    2 images (142 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 1.0 g of CO₂ per visit

    1.04 g

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

Accessibility

7 to fixGoogle 7888
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 8 text elements with low contrast

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

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 form fields without a label

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

  • 4 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 36 automated accessibility rules passed

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

SEO

5 to fixGoogle 9274
  • No H1 headline

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

  • No structured data

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

  • Meta description is long (444 characters)

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

  • 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://www.saintkentigern.com/sitemap.xml, so Google discovers your pages only by following links.

  • 227 internal links, 27 external

    The homepage links to 227 pages on saintkentigern.com and 27 external pages.

3 checks passed
  • Title: 39 characters

    Your title is a healthy 39 characters: “Homepage - Saint Kentigern Organisation”.

  • Canonical URL set

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

  • robots.txt in place

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

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

Other pages

5 to fix67
  • 1 page without a title

    https://www.saintkentigern.com/preschool/apply-now/preschool-virtual-tour has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://www.saintkentigern.com/preschool/apply-now/register-your-interest and https://www.saintkentigern.com/preschool/contact-us-2 all use the title “Saint Kentigern Enrolments”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.saintkentigern.com/preschool/apply-now/register-your-interest, https://www.saintkentigern.com/preschool/apply-now/preschool-virtual-tour and https://www.saintkentigern.com/preschool/contact-us-2 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.saintkentigern.com/apply-now and https://www.saintkentigern.com/girls-school use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://www.saintkentigern.com/preschool, https://www.saintkentigern.com/preschool/apply-now/register-your-interest, https://www.saintkentigern.com/preschool/apply-now/preschool-virtual-tour, https://www.saintkentigern.com/preschool/contact-us-2 and https://www.saintkentigern.com/girls-school have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.saintkentigern.com/preschool/apply-now/preschool-virtual-tour has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 pages slow to respond

    https://www.saintkentigern.com/preschool/uniform and https://www.saintkentigern.com/girls-school took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 7394
  • 5 third-party cookies

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

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

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 538 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “MAKE CONTACT” and “CONTACT FOUNDATION”.

  • 26 calls to action

    The homepage has 26 calls to action, for example “Apply Now”, “Contact” and “Register Your Interest”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 12 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

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

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
AWS

Company

Employees
560
Headquarters
Auckland

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on saintkentigern.com, including 16 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