Report loading
www.southcoastview.co.uk
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Good
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 website suffers from a critical structural deficiency in DOM size that threatens rendering performance and scalability across both desktop and mobile viewports.
South Coast View demonstrates exceptional technical foundations, specifically regarding Core Web Vitals where LCP, CLS, INP, and FCP all reside within the "Good" band. The site utilizes a sophisticated SEO metadata strategy through robust JSON-LD implementation for Person and Organization types, ensuring search engines understand the brand's core entities. On mobile, the user experience is further bolstered by highly visible navigation icons and a prominent, top-of-viewport call-to-action for Substack subscriptions.
A high-impact weakness exists in the excessive DOM size, which exceeds 4,100 nodes on both desktop and mobile, significantly increasing the computational cost of every layout pass and style recalculation. This technical debt is compounded by severe SEO omissions, including the total absence of H1 headings on primary pages and critically undersized title tags that fail to provide necessary search engine context. On desktop, secondary navigation text suffers from low visual contrast against the dark header, while the search functionality lacks an immediate, visible input field to facilitate user discovery.
The site presents a massive opportunity for organic growth by aligning its technical performance with proper semantic structure. By remediating the missing heading hierarchy and optimizing title tags, South Coast View leverages its existing high-speed loading capabilities to dominate search results. Additionally, refining the desktop header's visual balance and improving text readability on mobile hero images will directly increase user retention and conversion rates.
First 30 days:
5 highest-impact findings, ranked.
The search icon (magnifying glass) is present in the header but lacks an immediate text label or clear input field, which may require extra clicks for users to find and use.
How to fix: Consider adding a permanent search bar or a text label next to the search icon to improve discoverability for users who are not familiar with the icon alone.
On /privacy
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds. Fix any of the following: Element has insufficient color contrast of 4.48 (foreground color: #117cc2, background color: #ffffff, font size: 14.3pt (19px), font weight: normal). Expected contrast ratio of 4.5:1
How to fix: Element matching `#post-98162 > .ast-post-format-.blog-layout-1.ast-article-inner > .post-content.ast-col-md-12 > h2 > a[rel="bookmark"]` has contrast ratio 4.48; WCAG AA requires 4.5:1. Increase the contrast between foreground and background colours (the Tailwind hint below proposes the next darker step in the same family if the offending class is a recognised palette utility). Reference: https://dequeuniversity.com/rules/axe/4.11/color-contrast?application=playwright
On /news
Lighthouse flags DOMs above 1500 nodes as a performance concern and above 3000 as poor. Large trees slow every style recalculation and layout pass, balloon JS framework reconciliation cost, and inflate memory usage.
How to fix: Virtualise long lists (react-window, react-virtual), defer mounting of below-the-fold sections (Intersection Observer + lazy import), and avoid wrapping every primitive in <div>s — flatten the tree where possible.
On /
Lighthouse flags DOMs above 1500 nodes as a performance concern and above 3000 as poor. Large trees slow every style recalculation and layout pass, balloon JS framework reconciliation cost, and inflate memory usage.
How to fix: Virtualise long lists (react-window, react-virtual), defer mounting of below-the-fold sections (Intersection Observer + lazy import), and avoid wrapping every primitive in <div>s — flatten the tree where possible.
On /
Google typically displays 50–60 characters of the title in search results. A title under 30 chars usually fails to set context.
How to fix: Expand the title to 30–60 characters with the page topic and a brand suffix, e.g. <title>Page topic — Brand</title>.
On /privacy
