Website review, no card needed

openpolytechnic.ac.nz logo

openpolytechnic.ac.nz website review

Visit site (opens in a new tab)Reviewed 1 November 202640 issues · 87 checks

This review found 40 issues worth fixing on openpolytechnic.ac.nz, 18 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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.7 s3.5 sMay 9Oct 244.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.9 s
Jun 20, 20264.0 s
Jun 27, 20264.0 s
Jul 4, 20264.2 s
Jul 11, 20264.3 s
Jul 18, 20264.5 s
Jul 25, 20264.8 s
Aug 1, 20265.0 s
Aug 8, 20265.1 s
Aug 15, 20265.1 s
Aug 22, 20265.3 s
Aug 29, 20265.4 s
Sep 5, 20265.4 s
Sep 12, 20265.4 s
Sep 19, 20265.4 s
Sep 26, 20265.4 s
Oct 3, 20265.4 s
Oct 17, 20265.2 s
Oct 24, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
160 ms133 msMay 9Oct 24144 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026150 ms
May 16, 2026152 ms
May 23, 2026154 ms
May 30, 2026155 ms
Jun 6, 2026157 ms
Jun 13, 2026154 ms
Jun 20, 2026151 ms
Jun 27, 2026144 ms
Jul 4, 2026139 ms
Jul 11, 2026137 ms
Jul 18, 2026136 ms
Jul 25, 2026141 ms
Aug 1, 2026143 ms
Aug 8, 2026144 ms
Aug 15, 2026144 ms
Aug 22, 2026141 ms
Aug 29, 2026140 ms
Sep 5, 2026141 ms
Sep 12, 2026143 ms
Sep 19, 2026145 ms
Sep 26, 2026145 ms
Oct 3, 2026144 ms
Oct 17, 2026144 ms
Oct 24, 2026144 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 openpolytechnic.ac.nz (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. openpolytechnic.ac.nz at 1.0 s1.0 s
  2. openpolytechnic.ac.nz at 2.0 s2.0 s
  3. openpolytechnic.ac.nz at 3.0 s3.0 s
  4. openpolytechnic.ac.nz at 3.9 s3.9 s
  5. openpolytechnic.ac.nz at 4.9 s4.9 s
  6. openpolytechnic.ac.nz at 5.9 s5.9 s
  7. openpolytechnic.ac.nz at 6.9 s6.9 s
  8. openpolytechnic.ac.nz at 7.9 s7.9 s

Speed

6 to fix54
  • Use efficient cache lifetimes

    9.8 s · 2.3 MB

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

  • Reduce unused JavaScript

    2.1 s · 459 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 72 KiB

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

  • 2,880 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and monsido-consent.com and others), adding 405 KiB and 215 ms of main-thread time.

  • Improve image delivery

    195 KiB

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

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    29 KiB

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

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

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 192 ms

    192 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.0 s

    5.0 s

    Real visitors wait 5.0 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.4 s

    3.4 s

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

  • Largest Contentful Paint: 12.5 s

    12.5 s

    Your largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “banner image”.

  • Speed Index: 12.0 s

    12.0 s

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

  • Time to Interactive: 12.5 s

    12.5 s

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

  • Real-user CLS: 0.16

    0.16

    For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

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

    +30%

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

  • Cumulative Layout Shift: 0.195

    0.195

    The layout shifts by 0.195 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 2 images without width and height

    2 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 150 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user INP: 138 ms

    138 ms

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

  • Total Blocking Time: 114 ms

    114 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 91 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 91 requests on a phone: fonts 1.1 MB (15), scripts 824 KiB (27) and images 620 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

9 to fixGoogle 8589
  • 4 buttons without a name

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

  • Interactive controls must not be nested (51 elements)

    Interactive controls must not be nested: 51 elements on the page fail this check, rated serious by axe-core.

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

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (4 elements)

    Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • 10 H1 headlines

    There are 10 <h1> headlines (“.st0{fill:#FFFFFF;} .st1mym{font-family:'Newzald-…”, “.st0{fill:#FFFFFF;} .st1mymm{font-family:'Newzald…” and “.st0{fill:#FFFFFF;} .st1so{font-family:'National-…”). One clear main headline is easier for people and search engines.

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 365 internal links, 10 external

    The homepage links to 365 pages on openpolytechnic.ac.nz and 10 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Distance Learning with NZ's leading provider of distance and online learning. Certificates to degrees. Make your move a…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Distance Learning | Leading Online Study | Open Polytechnic NZ”.

  • Canonical URL set

    The canonical URL is https://www.openpolytechnic.ac.nz/.

  • Structured data in place

    Structured data found: WebPage.

  • robots.txt in place

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

  • XML sitemap found

    Your XML sitemap is reachable at http://www.openpolytechnic.ac.nz/sitemap.xml.

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.openpolytechnic.ac.nz/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 (1,877 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix43
  • 1 linked page is broken

    Your homepage links to https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/studying-by-distance-learning, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 10 pages without a title

    https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/get-prepared-for-study, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/how-much-time-will-you-need, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/about-our-qualifications, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/how-to-decide-what-to-study, https://www.openpolytechnic.ac.nz/study-with-us/study-support-and-resources and https://www.openpolytechnic.ac.nz/study-with-us/study-support-and-resources/how-well-support-your-studies and 4 others have no <title>, so Google invents the link text in results.

  • 10 linked pages hidden from search

    https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/get-prepared-for-study, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/how-much-time-will-you-need, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/about-our-qualifications, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/how-to-decide-what-to-study, https://www.openpolytechnic.ac.nz/study-with-us/study-support-and-resources and https://www.openpolytechnic.ac.nz/study-with-us/study-support-and-resources/how-well-support-your-studies and 4 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 10 pages without a meta description

    https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/get-prepared-for-study, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/how-much-time-will-you-need, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/about-our-qualifications, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/how-to-decide-what-to-study, https://www.openpolytechnic.ac.nz/study-with-us/study-support-and-resources and https://www.openpolytechnic.ac.nz/study-with-us/study-support-and-resources/how-well-support-your-studies and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/get-prepared-for-study, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/how-much-time-will-you-need, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/about-our-qualifications, https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us/how-to-decide-what-to-study, https://www.openpolytechnic.ac.nz/study-with-us/study-support-and-resources and https://www.openpolytechnic.ac.nz/study-with-us/study-support-and-resources/how-well-support-your-studies and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.openpolytechnic.ac.nz/study-with-us and https://www.openpolytechnic.ac.nz/study-with-us/distance-learning-with-us took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • 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.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 675 words of copy

    The homepage carries about 675 words of visible text.

4 checks passed
  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact”, “How to apply” and “How to apply to enrol”.

  • 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: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 3 cookies set on arrival

    3

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 openpolytechnic.ac.nz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Imperva

Company

Founded
1946

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on openpolytechnic.ac.nz, including 18 speed issues, 3 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