Universal Auto Parts

Your homepage loads over an insecure connection (http://universal.kiwi.nz/).

Why it matters: Browsers mark pages without HTTPS as not secure, and a visitor who sees that warning often leaves before reading anything.

How to fix it: Ask your web host or developer to install a free certificate and redirect every page to its https address.

Your site's security certificate did not validate when we read it.

Why it matters: A certificate that does not validate makes browsers show a full-page warning instead of your site.

How to fix it: Ask your host to reissue the certificate for your exact domain and check it covers both the www and bare address.

Your site does not tell browsers to always use the secure connection.

Why it matters: Without this instruction, a browser may still try the insecure address first, which leaves room for the connection to be tampered with.

How to fix it: Ask your developer or host to add the Strict-Transport-Security header once HTTPS works on every page.

Your site sends 0 of the 5 security headers we look for; missing: hsts, csp, x_frame_options, x_content_type_options, referrer_policy.

Why it matters: These headers tell browsers how to protect visitors - for example, stopping your pages being framed inside someone else's site.

How to fix it: Ask your developer or host to add the missing headers in the server or hosting settings.

Your domain does not publish an SPF record, so mail servers cannot tell which senders are genuinely yours.

Why it matters: Without it, your own emails are more likely to land in spam, and others find it easier to send mail that claims to come from you.

How to fix it: Add an SPF record in your domain's DNS settings; your email provider publishes the exact line to use.

Your domain does not publish a DMARC record, which lets anyone send email that claims to come from your domain.

Why it matters: A DMARC policy tells receiving mail servers what to do with mail that fails your checks, which protects your customers and your inbox placement.

How to fix it: Add a DMARC record in your DNS, starting with a monitoring policy, then tighten it once your legitimate mail passes.

Your site does not publish an llms.txt file.

Why it matters: An llms.txt file is a short, plain summary of your business and key pages that AI assistants can read quickly and quote accurately.

How to fix it: Create a text file at /llms.txt with a one-paragraph description of your business and links to your most important pages.

We found no sitemap for your site.

Why it matters: A sitemap lists every page you want found, so search engines and AI assistants do not miss the ones buried deep in your site.

How to fix it: Most website builders create a sitemap automatically; turn it on and list it in your robots.txt.

Your homepage carries no structured data.

Why it matters: Structured data describes your business in a form machines read directly, which is how search engines and AI assistants pick up your hours, address and services.

How to fix it: Add schema.org markup to your homepage; many website builders and SEO plugins do this for you.

Your structured data does not describe you as a business or organisation.

Why it matters: Marking up your business itself - name, address, phone, hours - is what lets AI assistants answer questions about you with confidence.

How to fix it: Add LocalBusiness (or Organization) markup with your name, address, phone number and opening hours.

We found no email address on your homepage.

Why it matters: An address people can copy or tap is the simplest way for a customer to get in touch on their own time.

How to fix it: Add your contact email to the homepage as text or a mailto link.

We found no contact form on your homepage.

Why it matters: A form lets a customer reach you at any hour without picking up the phone.

How to fix it: Add a simple contact form, or a clear link to one, on your homepage.

Your homepage does not declare its language.

Why it matters: Declaring the language helps screen readers pronounce your content and helps search engines show it to the right people.

How to fix it: Add a lang attribute to the page's html tag, for example en-NZ.

Your homepage is missing the tags that make a full preview when it is shared.

Why it matters: When someone shares your link, these tags decide the picture, title and description people see in the post.

How to fix it: Add Open Graph tags (title, description and image); most website builders have a social sharing setting for this.