Website review, no card needed
lpc.co.nz website review
Visit site (opens in a new tab)Reviewed 1 November 202644 issues · 84 checks
This review found 44 issues worth fixing on lpc.co.nz, 16 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 98 ms |
| May 16, 2026 | 97 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 101 ms |
| Jun 6, 2026 | 99 ms |
| Jun 13, 2026 | 100 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 98 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 97 ms |
| Aug 1, 2026 | 101 ms |
| Aug 8, 2026 | 108 ms |
| Aug 15, 2026 | 118 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 126 ms |
| Sep 5, 2026 | 119 ms |
| Sep 12, 2026 | 114 ms |
| Sep 19, 2026 | 103 ms |
| Sep 26, 2026 | 100 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 134 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
Speed
Use efficient cache lifetimes
1.4 s · 3.7 MB35 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).
Reduce unused JavaScript
1.6 s · 2.6 MBAbout 2.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
4.1 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.1 s.
omcinternational.com adds 1.2 s
1.2 somcinternational.com costs a phone 1.2 s of main-thread work and 2.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
2.3 MB7 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (omcinternational.com, YouTube and Google Tag Manager and others), adding 4.2 MB and 1.8 s of main-thread time.
Reduce unused CSS
900 ms · 324 KiBAbout 324 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Font display
800 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).
YouTube adds 399 ms
399 msYouTube costs a phone 399 ms of main-thread work and 992 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 452 ms. During a long task the page ignores taps.
Minify CSS
300 ms · 54 KiB54 KiB could be saved by minifying CSS.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
300 ms · 16 KiB16 KiB could be saved by minifying JavaScript.
Document request latency
33 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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: 366 ms
366 msYour server sent the HTML in 366 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Speed Index: 19.1 s
19.1 sVisually, the page fills in at 19.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 36.8 s
36.8 sThe page becomes fully interactive after 36.8 s. Good is under 3.8 s.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Lyttelton is the largest port in the South Island of New Ze…”. Most of its time is element render delay (5.6 s).
Tap response (INP) got 39% slower for real visitors
+39%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 98 ms to 134 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 521 ms
521 msScripts block taps and scrolling for 521 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Images and page weight
Page weight: 7.9 MB in 81 requests
7.9 MBYour homepage downloads 7.9 MB in 81 requests on a phone: scripts 4.0 MB (38), images 3.2 MB (16) and stylesheets 282 KiB (9). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.23 g of CO₂e: 267.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
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.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 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
Title is short (22 characters)
Your title is only 22 characters: “Lyttelton Port Company”. 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.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
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.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
118 internal links, 11 external
The homepage links to 118 pages on lpc.co.nz and 11 external pages.
5 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Lyttelton Port Company is the largest Port in the South Island of New Zealand. We are the gateway for the goods that ke…”.
Canonical URL set
The canonical URL is https://www.lpc.co.nz/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.lpc.co.nz/sitemap.xml.
AI search readiness
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.lpc.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.
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 (635 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://www.lpc.co.nz/port-map, https://www.lpc.co.nz/lpccareers, https://www.lpc.co.nz/filming-photography-and-drones, https://www.lpc.co.nz/about-us/publications and https://www.lpc.co.nz/our-services/cruise-ships have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.lpc.co.nz/about-us/hours-of-operation has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.lpc.co.nz/about-us/hours-of-operation and https://www.lpc.co.nz/about-us/news took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 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.
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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 small tap targets
2 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-images.mailchimp.com/embedcode/classic-061523.css' from origin 'https://www.lp…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 395 words of copy
The homepage carries about 395 words of visible text.
3 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Pricing Tariff”, “Talk to our Team” and “Contact”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 1 of them by other companies (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 lpc.co.nz, 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
- Hosting
- Google Cloud
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 lpc.co.nz, including 22 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.