landscapinglincolnshire.com
Garden Design and Landscaping | Fullers Landscaping
0 failed · 3 warnings · 26 passed
Audited Tue, 28 Jul 2026 16:15:06 GMT · https://www.landscapinglincolnshire.com/
Meta & Head
25/25
Title, description, canonical, social tags — what search engines read first.
Everything we check in this category passed.
Content & Structure
24.2/25
Headings, copy depth, images, structured data, internal linking.
Heading hierarchylow impactlow effort
Heading level jumps from h3 ("Our Customer Testimonials") to h5 ("Looking for a professional landscaping company in Lincolnshire and Newark? Contact Fullers Landscaping for a no-obligation proposal.")
Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.
7 passing checks
- Single H1 heading1 h1 found: "Award-Winning Garden Design and Landscaping in Lincolnshire"
- Word count6495 words of visible text
- Image alt text18 of 18 images have alt text
- Structured data (JSON-LD)JSON-LD types found: WebSite, WebSite
- HTML lang attribute<html lang="en">
- JavaScript-dependent contentvisible text ~6895 chars in the initial HTML
- Internal linking24 internal, 11 external links
Technical
23.3/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Short redirect chainmedium impactlow effort
https://gardenlandscapedesigners.com/ (301) → https://www.landscapinglincolnshire.com/
Every redirect hop adds a round-trip before the visitor sees anything, each hop can leak a little link equity, and crawlers abandon long chains — which can leave the destination page undiscovered. Trace the chain above and point the first URL directly at the final destination in a single 301; commonly this means merging separate http-to-https and non-www-to-www rules into one combined redirect. Also update internal links to reference the final URL directly, so most visitors never enter the chain at all.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
10 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Fast time to first byte185 ms
- Reasonable HTML size870.7 KB
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.