Website review, no card needed

tepuia.com logo

tepuia.com website review

Visit site (opens in a new tab)Reviewed 19 October 202642 issues · 88 checks

This review found 42 issues worth fixing on tepuia.com, 13 of them high impact, across 88 checks. The most urgent: improve image delivery. 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.4 s1.9 sApr 25Oct 102.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.2 s
May 2, 20262.3 s
May 9, 20262.4 s
May 16, 20262.3 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20262.0 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
271 ms157 msApr 25Oct 10258 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026171 ms
May 2, 2026172 ms
May 9, 2026172 ms
May 16, 2026175 ms
May 23, 2026175 ms
May 30, 2026177 ms
Jun 6, 2026170 ms
Jun 13, 2026170 ms
Jun 20, 2026171 ms
Jun 27, 2026171 ms
Jul 4, 2026180 ms
Jul 11, 2026186 ms
Jul 18, 2026185 ms
Jul 25, 2026186 ms
Aug 1, 2026187 ms
Aug 8, 2026188 ms
Aug 15, 2026196 ms
Aug 22, 2026201 ms
Aug 29, 2026206 ms
Sep 5, 2026209 ms
Sep 12, 2026211 ms
Sep 19, 2026227 ms
Sep 26, 2026237 ms
Oct 3, 2026246 ms
Oct 10, 2026258 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 tepuia.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tepuia.com at 1.2 s1.2 s
  2. tepuia.com at 2.5 s2.5 s
  3. tepuia.com at 3.7 s3.7 s
  4. tepuia.com at 5.0 s5.0 s
  5. tepuia.com at 6.2 s6.2 s
  6. tepuia.com at 7.4 s7.4 s
  7. tepuia.com at 8.7 s8.7 s
  8. tepuia.com at 9.9 s9.9 s

Speed

11 to fix39
  • Improve image delivery

    2.1 s · 1.2 MB

    16 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Render-blocking requests

    2.8 s

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

  • Mobile performance score: 39

    39/100

    Your mobile performance score is 39 (desktop: 58). 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 CDN, Facebook and Google Tag Manager and others), adding 2.7 MB and 1.8 s of main-thread time.

  • Reduce unused JavaScript

    600 ms · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Use efficient cache lifetimes

    900 ms · 650 KiB

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

  • Google CDN adds 581 ms

    581 ms

    Google CDN costs a phone 581 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.

  • Facebook adds 404 ms

    404 ms

    Facebook costs a phone 404 ms of main-thread work and 361 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 395 ms

    395 ms

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

  • Main-thread work: 3.9 s

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

  • awswaf.com adds 174 ms

    174 ms

    awswaf.com costs a phone 174 ms of main-thread work and 413 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.

  • Legacy JavaScript

    200 ms · 31 KiB

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

  • Reduce unused CSS

    150 ms · 58 KiB

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 36 KiB

    36 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 18 ms

    18 ms

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

  • Largest Contentful Paint: 9.8 s

    9.8 s

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

  • Time to Interactive: 25.5 s

    25.5 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Total Blocking Time: 838 ms

    838 ms

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 251 ms

    251 ms

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

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

    +47%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • 4 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-10, 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).

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

    0.006

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

Images and page weight

3 to fix53
  • Page weight: 5.5 MB in 153 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 153 requests on a phone: scripts 2.9 MB (66), images 1.8 MB (35) and other files 373 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (1.3 MB) 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.

  • 5 images below the first screen load straight away

    5 images further down the page (821 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.56 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

7 to fixGoogle 8491
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

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

  • 7 images without alt text

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

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

  • 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
  • 47 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: 47 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 7795
  • No social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 44 internal links, 14 external

    The homepage links to 44 pages on tepuia.com and 14 external pages.

7 checks passed
  • Meta description: 106 characters

    Your meta description is 106 characters: “Discover Te Puia Rotorua, home to world-famous Pōhutu Geyser, Māori culture, NZMACI and kiwi conservation.”.

  • One H1 headline

    Your main headline reads: “Māori Culture, Geothermal Wonders and Kiwi Conservation”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Te Puia Rotorua – Pōhutu Geyser, Māori Culture & Kiwi”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, LocalBusiness, Organization, TouristAttraction and 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 https://www.tepuia.com/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.tepuia.com/llms.txt (3 KiB, 28 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.tepuia.com/news is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.tepuia.com/nz-maori-arts-crafts has 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 17 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 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”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix90
  • Thin social proof

    Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 225 words

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

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

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK NOW”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Book Now” and “Get in touch”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.

  • 9 cookies set on arrival

    9

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

  • 32 other companies contacted

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on tepuia.com, including 23 speed issues, 2 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