Website review, no card needed
darwin.nt.gov.au website review
Visit site (opens in a new tab)Reviewed 28 October 202644 issues · 87 checks
This review found 44 issues worth fixing on darwin.nt.gov.au, 17 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 126 ms |
| May 16, 2026 | 129 ms |
| May 23, 2026 | 136 ms |
| May 30, 2026 | 135 ms |
| Jun 6, 2026 | 140 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 139 ms |
| Jul 4, 2026 | 140 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 148 ms |
| Sep 5, 2026 | 149 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 156 ms |
| Sep 26, 2026 | 155 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 165 ms |
| Oct 24, 2026 | 170 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
How it loaded on a phone
0.6 s
1.2 s
1.7 s
2.3 s
2.9 s
3.5 s
4.0 s
4.6 s
Speed
Use efficient cache lifetimes
16.1 s · 7.5 MB96 files are served with short cache lifetimes, so returning visitors download them again (7.5 MB).
Improve image delivery
13.1 s · 5.1 MB42 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.1 s faster on a phone.
Render-blocking requests
3.4 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Reduce unused JavaScript
2.5 s · 504 KiBAbout 504 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 52). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,359 HTML elements
The page has 5,359 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
950 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 950 ms).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and userway.org and others), adding 1.2 MB and 789 ms of main-thread time.
Reduce unused CSS
450 ms · 113 KiBAbout 113 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 417 ms
417 msGoogle Tag Manager costs a phone 417 ms of main-thread work and 616 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.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 357 ms. During a long task the page ignores taps.
Facebook adds 251 ms
251 msFacebook costs a phone 251 ms of main-thread work and 336 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
34 KiBPolyfills for old browsers add 34 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.
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: 18 ms
18 msYour server sent the HTML in 18 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.
Largest Contentful Paint: 40.4 s
40.4 sYour largest element takes 40.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “City of Darwin Image Library”.
Time to Interactive: 41.5 s
41.5 sThe page becomes fully interactive after 41.5 s. Good is under 3.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 884 ms
884 msScripts block taps and scrolling for 884 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 204 ms
204 msReal visitors wait 204 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 126 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
3 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user TTFB: 663 ms
663 msReal visitors wait 663 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.021
0.021The layout barely moves while loading (CLS 0.021, good is under 0.1).
Images and page weight
Page weight: 9.1 MB in 147 requests
9.1 MBYour homepage downloads 9.1 MB in 147 requests on a phone: images 7.4 MB (81), scripts 1.3 MB (26) and fonts 158 KiB (6). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
1.7 MB6 images are downloaded at several times the size a phone draws them, for example Untitled design (3).png at 1,920 px wide, shown at 390 px. Resized copies would save about 1.7 MB.
1 image over 500 KB
Untitled design (3).png weighs 1.2 MB. On a phone connection a single image that size takes seconds.
9 images in older formats
9 images (2.8 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.
About 2.6 g of CO₂ per visit
2.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.58 g of CO₂e: 309.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (1 element).
2 checks passed
Every image has alt text
All 50 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
87 links crawlers can't follow
87 links have no real href, so search engines can't follow them.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.
12 links with vague text
12 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.
1,003 internal links, 26 external
The homepage links to 1,003 pages on darwin.nt.gov.au and 26 external pages.
4 checks passed
Title: 51 characters
Your title is a healthy 51 characters: “City of Darwin | Darwin Council, Northern Territory”.
Canonical URL set
The canonical URL is https://www.darwin.nt.gov.au/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.darwin.nt.gov.au/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.darwin.nt.gov.au/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 (4,571 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://www.darwin.nt.gov.au/libraries, https://www.darwin.nt.gov.au/libraries/about/contact-libraries and https://www.darwin.nt.gov.au/libraries/children-young-people/early-literacy-programs have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages slow to respond
https://www.darwin.nt.gov.au/libraries/about, https://www.darwin.nt.gov.au/libraries/about/contact-libraries, https://www.darwin.nt.gov.au/libraries/about/libraries-policies, https://www.darwin.nt.gov.au/libraries/kids-and-teens and https://www.darwin.nt.gov.au/libraries/kids-and-teens/steam-programs took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
6 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
53 of 54 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 1,447 words of copy
The homepage carries about 1,447 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: “Call” and “Learn More”.
41 calls to action
The homepage has 41 calls to action, for example “Call”, “Contact Us” and “Contact Libraries”.
2 short forms
2 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
23 other companies contacted
Loading the homepage contacts 23 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 darwin.nt.gov.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Wholesale Services Provider
Company
- Founded
- 1869
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 darwin.nt.gov.au, including 24 speed issues, 6 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.