Report loading
pickld.com.au
Preparing the full page inventory and screenshots.
Score
49
Issues
Analyzed
Report loading
Preparing the full page inventory and screenshots.
Poor
Health Score
Score by category
The headline health score combines page-level quality and site-wide repeat patterns, then stays anchored to the weakest visible category so it never looks worse than every category beneath it.
Section 01
The Pickld website is currently experiencing a critical service interruption that renders the entire digital presence inaccessible to both users and search engines.
The site demonstrates a proactive approach to AI readiness, with a functional robots.txt that allows major AI crawlers and a sitemap index that facilitates discovery. On mobile, the presence of a high-impact discount popup indicates an existing strategy for lead capture and conversion optimization.
The most severe issue is a critical server error (HTTP 503) affecting the homepage on both desktop and mobile. This error prevents all visitors from accessing the site and stops answer engines from indexing or citing the brand. Furthermore, the site lacks essential security headers, specifically a Content-Security-Policy and Strict-Transport-Security, which exposes the infrastructure to injection and protocol downgrade attacks.
There is a significant opportunity to optimize for the next generation of search. While the site is technically accessible to AI agents, the content lacks the structured data (JSON-LD), semantic hierarchy, and specific commercial answer blocks required for high-quality citations in AI-driven search results. Strengthening entity clarity and adding FAQ-style blocks would position Pickld as a primary source for AI-generated summaries.
To restore operations and protect the brand, the following actions must be taken within the next 30 days:
5 highest-impact findings, ranked.
The origin server accepted the request but returned a 5xx status, indicating an unhandled server-side error. Visitors hitting this URL will see the browser's error page or whatever fallback the host serves on 5xx. The remaining audit dimensions on this page were not assessed because no usable content was returned.
How to fix: Check the application logs for this route around the scan timestamp. Common causes include unhandled exceptions in server code, database connection failures, missing environment variables in the deployment, and exhausted resource limits. Re-run the scan once the route serves a 2xx.
On /
No HSTS header. Users are vulnerable to protocol downgrade attacks.
How to fix: Add: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
On /
No CSP header found. The site is vulnerable to XSS and injection attacks.
How to fix: Add a Content-Security-Policy header. Start restrictive: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'
On /
Third-party scripts (analytics, embeds, ad pixels, font CDNs, chat widgets) are hosted outside your control and often render-block, INP-block, or both. Each adds DNS resolution + TLS overhead and can fail independently of your own infrastructure.
How to fix: Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
On /
The page at https://pickld.com.au/ returned a 503 status code.
How to fix: Investigate the server error and ensure the page loads correctly.
On /
