No checks match that filter.
Full diagnostics
Every check that ran, grouped by what it affects. Problems appear first in each group.
Meta Tags & Search Snippet Simulator
The tags that decide how this page is titled and described in search results.
Professionally Qualified and Accredited Genealogy, Family and Local History Research Service. Based in Scottish Borders Northumberland and Durham
Professionally Qualified and Accredited Genealogy, Family and Local History Research Service. Based in Scottish Borders Northumberland and Durham
Title width
2164px of 580px
The title is about 2164px wide and will be truncated in desktop results (limit 580px).
Rendered width
Desktop 2164px / 580px Mobile 1947px / 920px
Measured in Arial at the size Google renders result titles,
accurate to within a fraction of a percent of a browser. Characters: 234.
How to fix
Rendered width
| Desktop | 2164px | / 580px | |
| Mobile | 1947px | / 920px |
Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 234.
The meta description length is well judged.
Nothing in this section matches the current filter.
Crawling & indexing
Whether search engines can reach, read and index this page at all.
Canonical tag
No canonical tag, so duplicate URLs may compete with each other.
How to fix
Redirect chain
1 redirects
The URL redirects once before resolving, costing an extra round trip.
301 https://bordersancestry.com/
200 https://www.bordersancestry.com/
How to fix
Favicon
No favicon is declared. Google shows one beside your result on mobile.
How to fix
www and https versions
1 found
The other spellings of this address arrive here, but not in one permanent step: a chain costs time on every visit, and a temporary redirect tells search engines the move may not last.
http://bordersancestry.com/ → 301 → 301 → https://www.bordersancestry.com/ (2 redirects)
How to fix
The page returns 200 OK.
No directive prevents indexing.
Language is declared as "en".
lang="en"
No hreflang annotations, which is correct for a single-language page.
The viewport is configured for mobile.
width=device-width, initial-scale=1.0
The page declares UTF-8 encoding.
All resources load securely.
The URL is 32 characters.
The URL is clean and readable.
The page is 0 levels deep.
The URL has no query parameters.
robots.txt is present and does not block crawling.
A sitemap is published, listing 153 URLs.
Lists 153 URLs
A page that does not exist returns HTTP 404, so search engines drop dead addresses.
Nothing in this section matches the current filter.
Content & metadata
What the page says it is about, and how it reads.
H1 tag
The page has no h1, so its main subject is undeclared.
How to fix
Keyword repetition
"arrow" makes up 7.0% of the page text, which reads as unnatural repetition rather than writing.
Where these terms appear
Term Count Density
arrow 17 7.02%
How to fix
Where these terms appear
| Term | Count | Density |
|---|---|---|
| arrow | 17 | 7.02% |
Share image
140 × 35 px
The share image is 140 × 35 pixels. Under 600 × 315, platforms show a small thumbnail beside the link instead of a large card.
https://www.bordersancestry.com/uploads/1/7/2/3/17231010/editor/rqg-b-w-logo.png?1569675911
How to fix
Twitter card
No twitter:card tag, so shared links render as a small preview.
How to fix
Text-to-HTML ratio
2.0% text
Only 2.0% of the page is readable text; the rest is markup and script.
How to fix
Open Graph tags are present.
The heading outline descends in order.
The page has roughly 396 words.
No data tables on this page, so there are no columns to label.
The page's prominent terms appear in its title, description or headings.
Where these terms appear
| Term | Count | Density | Title | Description | Headings |
|---|---|---|---|---|---|
| arrow | 17 | 7.02% | ✕ | ✕ | ✕ |
| borders | 6 | 2.48% | ✓ | ✓ | ✓ |
| ancestry | 6 | 2.48% | ✓ | ✕ | ✓ |
| norham | 6 | 2.48% | ✕ | ✕ | ✕ |
| newsletter | 5 | 2.07% | ✕ | ✕ | ✕ |
The page's most frequent terms, from 242 words of content.
What this page is about
Term size reflects how often it appears. Density is not a ranking factor, this is a view of the page's subject, not a target to hit.
Nothing in this section matches the current filter.
AI & answer readiness
Whether answer engines and AI overviews can extract and trust this page.
Answer readiness
0 found
No heading is followed by a concise 40 to 60 word answer, the shape featured snippets and AI overviews extract.
How to fix
Content freshness
The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.
How to fix
Answer schema
No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.
How to fix
llms.txt for AI agents
No llms.txt. AI coding agents have no curated map of this site.
https://www.bordersancestry.com/llms.txt returned nothing
How to fix
Attribution signals present: about page, contact page, privacy policy.
about page, contact page, privacy policy
396 words across 4 headings, 25 lists and 0 tables.
The page has no structured data, so there is no entity to check.
The page reads the same with and without JavaScript.
Every AI crawler checked is allowed to read this page.
Nothing in this section matches the current filter.
Speed & delivery
What makes the page slow, and what the loading experience measures.
Largest Contentful Paint
Target ≤ 2.5s
What this measures
How long until the largest thing on screen, usually the hero image, video or headline block, has finished rendering. It is a proxy for "when did this page feel loaded".
What moves it: Serve the hero image in a modern format at the size it is displayed, preload it, and remove render-blocking CSS and JavaScript ahead of it. A slow server response delays it too, so check TTFB first.
Interaction to Next Paint
Target ≤ 200ms
What this measures
How long the page takes to respond visibly after a tap, click or key press, measured across every interaction, not just the first. High INP is what makes a page feel unresponsive even once it looks ready.
What moves it: Break up long JavaScript tasks so the main thread is free to respond, defer work that is not needed for the interaction, and avoid large re-renders on every event.
Cumulative Layout Shift
Target ≤ 0.1
What this measures
How much visible content jumps around while the page loads. This is what makes someone tap the wrong thing because a banner or image pushed the layout down underneath their finger.
What moves it: Give images and video explicit width and height so the browser reserves the space, reserve room for ads and embeds, and avoid inserting content above what is already on screen.
First Contentful Paint
Target ≤ 1.8s
What this measures
How long until anything at all appears, the first text or image painted. It separates "the page starts slowly" from "the biggest element is slow": a fast FCP with a slow LCP points at the hero, while both slow points at the server.
What moves it: Cut render-blocking CSS and JavaScript in the head, inline the styles needed for the first screen, and improve the server response time.
Real-user response time
Target ≤ 800ms
Needs real-user data from Chrome UX Report
Render-blocking resources
22 found
22 resources in <head> block the first paint, delaying when anything appears on screen.
stylesheet: //cdn2.editmysite.com/css/sites.css?buildtime=1780340638
stylesheet: //cdn2.editmysite.com/css/old/fancybox.css?buildtime=1780340638
stylesheet: /files/main_style.css?1780349974
stylesheet: //cdn2.editmysite.com/fonts/Poppins/font.css?2
stylesheet: //cdn2.editmysite.com/fonts/Open_Sans/font.css?2
stylesheet: //cdn2.editmysite.com/fonts/Open_Sans/font.css?2
How to fix
Third-party services
5 services · 1.4 MB
5 third-party services account for 78% of what this page downloads, 1.4 MB and 1.1s of main-thread time.
Third-party services
Service Transferred Main thread
Weebly 1.1 MB 792ms Google Tag Manager 288 KB 296ms weebly.com 6 KB 9ms Google Fonts 2 KB under 1ms Google Analytics 1 KB under 1ms
1.1s of main-thread time
How to fix
Third-party services
| Service | Transferred | Main thread | |
|---|---|---|---|
| Weebly | 1.1 MB | 792ms | |
| Google Tag Manager | 288 KB | 296ms | |
| weebly.com | 6 KB | 9ms | |
| Google Fonts | 2 KB | under 1ms | |
| Google Analytics | 1 KB | under 1ms |
Browser caching
99 KB re-downloaded
31 files have cache lifetimes short enough that returning visitors download 99 KB again.
Short cache lifetimes
File Cache lifetime Size
cdn2.editmysite.com/main-customer-accounts-site.js 14d 156 KB cdn2.editmysite.com/main.js 14d 145 KB cdn2.editmysite.com/stl.js 14d 34 KB cdn2.editmysite.com/jquery-1.8.3.min.js 14d 33 KB cdn2.editmysite.com/sites.css 14d 30 KB cdn2.editmysite.com/italic.woff2 14d 18 KB cdn11.editmysite.com/commerce-core.js 14d 18 KB cdn2.editmysite.com/bolditalic.woff2 14d 18 KB cdn11.editmysite.com/main-commerce-browse.js 14d 17 KB cdn2.editmysite.com/regular.woff2 14d 17 KB cdn2.editmysite.com/bold.woff2 14d 17 KB www.bordersancestry.com/plugins.js none 16 KB
Showing the 12 largest of 31 files.
8 expire within the hour
How to fix
Short cache lifetimes
| File | Cache lifetime | Size |
|---|---|---|
| cdn2.editmysite.com/main-customer-accounts-site.js | 14d | 156 KB |
| cdn2.editmysite.com/main.js | 14d | 145 KB |
| cdn2.editmysite.com/stl.js | 14d | 34 KB |
| cdn2.editmysite.com/jquery-1.8.3.min.js | 14d | 33 KB |
| cdn2.editmysite.com/sites.css | 14d | 30 KB |
| cdn2.editmysite.com/italic.woff2 | 14d | 18 KB |
| cdn11.editmysite.com/commerce-core.js | 14d | 18 KB |
| cdn2.editmysite.com/bolditalic.woff2 | 14d | 18 KB |
| cdn11.editmysite.com/main-commerce-browse.js | 14d | 17 KB |
| cdn2.editmysite.com/regular.woff2 | 14d | 17 KB |
| cdn2.editmysite.com/bold.woff2 | 14d | 17 KB |
| www.bordersancestry.com/plugins.js | none | 16 KB |
Showing the 12 largest of 31 files.
Deprecated tags
The page uses <font> removed from HTML5, which browsers render inconsistently.
<font> × 13
How to fix
Inline styles
100 found
100 elements carry inline style attributes, which cannot be cached and inflate the document.
How to fix
Time to first byte is 165 ms.
The HTML document is 105 KB.
The response is compressed with gzip.
Content-Encoding: gzip
The page loads 55 requests totalling 1.8 MB.
What loaded, by type
| Type | Requests | Transferred | |
|---|---|---|---|
| script | 21of 18 declared | 1.2 MB | |
| image | 2of 1 declared | 353 KB | |
| font | 10 | 125 KB | |
| stylesheet | 12of 16 declared | 115 KB | |
| document | 2 | 24 KB | |
| other | 8 | 7 KB |
Of these, 41 requests (1.4 MB) come from third-party domains.
Nothing in this section matches the current filter.
Security
Transport security, reputation and the response headers that protect visitors.
HSTS
No Strict-Transport-Security header, so a first visit over HTTP can be intercepted before the redirect.
How to fix
Clickjacking protection
Nothing prevents this page being embedded in a frame, which allows clickjacking.
How to fix
Email addresses in the page
1 found
1 email address is written into the page as plain text, where harvesting bots collect them for spam and phishing.
[email protected]
How to fix
MIME sniffing
No X-Content-Type-Options header, so browsers may guess a resource type and execute it.
How to fix
Referrer policy
No Referrer-Policy header, so full URLs may leak to third-party sites.
How to fix
Content Security Policy
No Content-Security-Policy, the main defence against cross-site scripting.
How to fix
Permissions policy
No Permissions-Policy header, so any script or embed on the page may ask for the camera, microphone or location.
How to fix
security.txt
No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.
https://www.bordersancestry.com/.well-known/security.txt
How to fix
The cookie the page sets carries Secure, HttpOnly and SameSite.
No software versions are disclosed in headers or the page.
The TLS certificate is valid for another 67 days, issued by Google Trust Services.
67 days remaining
Not listed by Google Web Risk for malware, phishing or unwanted software.
Connections use TLS 1.3.
Nothing in this section matches the current filter.
Server & domain
The server and the domain behind the page: protocol, network, registration and email records.
IPv6
www.bordersancestry.com has no IPv6 address. Visitors on IPv6-only mobile networks reach it through a translation gateway, which adds a step.
How to fix
DMARC policy
bordersancestry.com has no DMARC record, so mail servers have no instruction for mail that fails SPF or DKIM. Gmail and Yahoo require one from bulk senders.
How to fix
Served over HTTP/2, which loads a page's files in parallel over one connection.
Served through Cloudflare, a CDN, so visitors get the page from a server near them.
bordersancestry.com is registered until 2 Feb 2030 with Mesh Digital Limited.
1177 days remaining
bordersancestry.com was registered on 2 Feb 2015, 11 years ago. Age is not a ranking factor, but an established name is one buyers and partners look for.
bordersancestry.com publishes an SPF record: v=spf1 include:spf.protection.outlook.com -all
No ad network loads on this page, so ads.txt is not needed.
Nothing in this section matches the current filter.
Links, media & schema
Links, images and structured data.
Anchor text
2 found
2 links have no anchor text, so its purpose is unreadable without sight of the layout.
All 2 point at the same destination, one template reused down the page.
Line Link
656, 661 # ×2<a href="#" class="search-toggle"> <svg class="icon-search" width="20" height="20" viewbox="0 0 20 20" xmlns="http://www.w3.org/2000/svg"><path d="M19.51 17.147l-4.344-4.345c-.023-.023-.05-.04-.075-.06.856-1.297 1.355-2.85 1.355-4.52 0-4.54-3.68-8.222-8.222-8.222S0 3.68 0 8.223c0 4.54 3.68 8.222 8.…
How to fix
All 2 point at the same destination, one template reused down the page.
| Line | Link |
|---|---|
| 656, 661 | # ×2<a href="#" class="search-toggle"> <svg class="icon-search" width="20" height="20" viewbox="0 0 20 20" xmlns="http://www.w3.org/2000/svg"><path d="M19.51 17.147l-4.344-4.345c-.023-.023-.05-.04-.075-.06.856-1.297 1.355-2.85 1.355-4.52 0-4.54-3.68-8.222-8.222-8.222S0 3.68 0 8.223c0 4.54 3.68 8.222 8.… |
Image dimensions
1 found
1 image has no width and height, so the page shifts as they load (hurting CLS).
# / line Image source
#1 L756 /uploads/1/7/2/3/17231010/editor/rqg-b-w-logo.png?1569675911<img src="/uploads/1/7/2/3/17231010/editor/rqg-b-w-logo.png?1569675911" alt="Picture Susie Douglas Qualified Genealogist Family Historian and Writer https://www.qualifiedgenealogists.org/profiles/douglas-susie" style="width:auto;max-width:100%">
How to fix
| # / line | Image source |
|---|---|
| #1 L756 | /uploads/1/7/2/3/17231010/editor/rqg-b-w-logo.png?1569675911<img src="/uploads/1/7/2/3/17231010/editor/rqg-b-w-logo.png?1569675911" alt="Picture Susie Douglas Qualified Genealogist Family Historian and Writer https://www.qualifiedgenealogists.org/profiles/douglas-susie" style="width:auto;max-width:100%"> |
Broken links
20 checked
1 link on this page return an error, 1 of them to this site's own pages. Visitors who follow it land on an error page.
403 https://www.bordersancestry.com/store/checkout?cart=
How to fix
Structured data
The page has no structured data, so it cannot qualify for rich results.
How to fix
66 internal and 3 external links.
66 internal, 3 external
66 internal, 3 external
Outbound link rel attributes look appropriate.
In-page anchors resolve to real targets.
All images carry an alt attribute.
No heavy legacy image formats found.
Image loading strategy looks sound.
Images are served responsively or are small enough not to need it.
Nothing in this section matches the current filter.
What to fix first
Ranked by impact against effort, the top of this list buys the most for the least work.
Score breakdown
How each area scored. Categories that could not be measured are excluded rather than counted as zero.