| Page Title | Page Title tips for settled.govt.nz: An effective website title should not exceed 60 characters to prevent truncation in search engine results pages (SERPs), maintaining full clickability and ensuring the entire compelling headline is visible to potential visitors seeking your specific products or services online. |
|---|
| Length: 22 characters |
| Meta Description | Meta Description tips for settled.govt.nz: A meta description's primary goal is not just SEO, but conversion; crafting compelling copy that speaks directly to the target audience's needs and includes relevant keywords helps boost click-through rates and drive qualified traffic. |
|---|
| Length: 151 characters |
| Meta Keywords | Meta Keywords tips for settled.govt.nz: The fundamental shift away from meta keywords reflects search engines moving towards understanding user intent and content quality, rather than simply matching isolated keyword phrases anywhere on the page. |
|---|
no meta keywords data for settled.govt.nz 2026-09-01T18:58:19+00:00 |
| Page Content | Page Content tips for settled.govt.nz: Ensure all page content is meticulously proofread for spelling and grammatical errors, and verify all facts presented are accurate and well-researched to maintain credibility and trustworthiness with both users and search engines. |
|---|
| Web Page Content Length: 282899 characters |
| H1 Heading | H1 Heading tips for settled.govt.nz: A well-chosen H1 header not only improves user experience by providing immediate context and setting expectations for the content below but also acts as a primary ranking factor for search engines seeking to understand the page's central theme effectively. |
|---|
| Count: 1 heading tag |
| H2 Headings | H2 Headings tips for settled.govt.nz: Incorporate secondary keywords naturally within your H2 header text, ensuring these terms align with your primary focus and target audience's search intent, thereby boosting semantic relevance and potentially improving the page's ranking for related long-tail queries. |
|---|
| Count: 18 heading tag |
| H3 Headings | H3 Headings tips for settled.govt.nz: Employ H3 tags to create clear section breaks in tutorials or step-by-step guides, visually distinguishing instructions and aiding the reader's comprehension process. |
|---|
| Count: 4 heading tag |
| H4 Headings | H4 Headings tips for settled.govt.nz: Employing H4 tags consistently for related sub-sections enhances the logical flow and coherence of your web content, making it more digestible for human readers and aiding search engine content comprehension |
|---|
| Count: 6 heading tag |
| H5-H6 Headings | H5-H6 Headings tips for settled.govt.nz: Consistent and proper semantic use of HTML headers, including H5 and H6, is crucial for accessibility tools like screen readers to accurately convey document structure to users. |
|---|
no h5-h6 headings data for settled.govt.nz 2026-09-01T18:58:19+00:00 |
| Image ALT Attributes | Image ALT Attributes tips for settled.govt.nz: Ensure that image ALT text accurately conveys the visual information provided by the image, avoiding misleading descriptions that could negatively impact user engagement and SEO credibility. |
|---|
no image alt attributes data for settled.govt.nz 2026-09-01T18:58:19+00:00 |
| Robots.txt | Robots.txt tips for settled.govt.nz: Even if a page is blocked by robots.txt, a search engine might still discover it through other links, so ensure its content isn't marked with meta robots noindex tags if public access is intended. |
|---|
| file robots.txt was found on the website |
| XML Sitemap | XML Sitemap tips for settled.govt.nz: Incorporate your meticulously formatted XML sitemap URL into your initial website deployment process and submit it to relevant search engines like Google via Google Search Console to accelerate the initial crawling and indexing phase. |
|---|
no xml sitemap data for settled.govt.nz 2026-09-01T18:58:19+00:00 |
| Page Size | Page Size tips for settled.govt.nz: Consider implementing server-side rendering or progressive web app techniques to deliver a core HTML payload more quickly, bypassing the reliance solely on minimizing page size through client-side optimization. |
|---|
| page size: 276 kb |
| Response Time | Response Time tips for settled.govt.nz: Avoiding high server response times is vital for maintaining good SEO signals; conduct regular performance audits focusing on reducing backend processing delays to keep search rankings high. |
|---|
| response time: 4.793 sec |
| Minify CSS | Minify CSS tips for settled.govt.nz: Failure to minify critical CSS can lead to slower loading times, negatively impact user satisfaction, increase bounce rates, and ultimately harm your website's search engine rankings and visibility. |
|---|
| included in the page |
| Minify JavaScript | Minify JavaScript tips for settled.govt.nz: Enhance your website's loading speed and SEO by automatically minifying JavaScript source code, eliminating all unnecessary characters and formatting, resulting in smaller file sizes, quicker page loads, improved Core Web Vitals, and better search rankings. |
|---|
| detected during site scan |
| Structured Data | Structured Data tips for settled.govt.nz: Ensure your website's Product Schema is comprehensive by including all necessary details like manufacturer part numbers, GTINs (UPCs/EANs), colors, sizes, and variations, which helps search engines understand product specifics and potentially surface your items in comparison shopping results. |
|---|
no structured data data for settled.govt.nz 2026-09-01T18:58:19+00:00 |
| CDN Usage | CDN Usage tips for settled.govt.nz: Choose a CDN that integrates smoothly with your Content Management System (CMS) to simplify configuration and potentially automate cache invalidation processes, ensuring content updates are quickly reflected without manual intervention. |
|---|
no cdn usage data for settled.govt.nz 2026-09-01T18:58:19+00:00 |
| SSL certificates | SSL certificates tips for settled.govt.nz: When setting up new websites, configuring an SSL certificate from day one is a critical foundational step that prevents future migration headaches and establishes initial trust and security, aligning perfectly with modern SEO best practices. |
|---|
| SSL is enabled on the website |