repromed.co.nz website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user FCP: 3.2 s

  3.2 s

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

• Real-user TTFB: 2.6 s

  2.6 s

  Real visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 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.

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

  +107%

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

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

  +12%

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

• Page weight: 4.6 MB

  4.6 MB

  Your homepage downloads 4.6 MB on a phone, 1.5 MB of it images (33%). Under 2 MB keeps phones on slow connections fast.

• 3 images in older formats

  3 images (173 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.

  Elements (3)

• 4 images below the first screen load straight away

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

  Elements (4)

• About 1.3 g of CO₂ per visit

  1.29 g

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

• Invalid ARIA attributes

  2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  Elements (2)

• 4 tap targets too small

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

  Elements (3)

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

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

  Elements (3)

• The skip-link target should exist and be focusable (1 element)

  The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 2 links without text

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

  Elements (2)

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

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

  Elements (3)

• Headings skip levels

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

  View sourceElements (1)

• 176 internal links, 10 external

  The homepage links to 176 pages on repromed.co.nz and 10 external pages.

• Organization data is thin (3 of 6 facts)

  Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  View source

• No llms.txt

  There is no https://www.repromed.co.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.

• 1 page with very little text

  https://www.repromed.co.nz/chinese 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.

• 3 pages slow to respond

  https://www.repromed.co.nz/about-repromed/our-success-rates, https://www.repromed.co.nz/about-repromed/careers and https://www.repromed.co.nz/about-repromed/privacy-policy took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Unexpected token ':'”.

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

  View source

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

  The homepage carries about 618 words of visible text.

• 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 Microsoft Clarity (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.

• 8 cookies set on arrival

  8

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

• 15 other companies contacted

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