SEO report for www.splitframeofreference.com
https://www.splitframeofreference.com/ · checked Thu, 05 Nov 2026 02:33 GMT
Fix these first
- Meta descriptionhigh
No meta description – Google will pick text from the page.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
On Squarespace: Pages panel → gear icon on the page → SEO tab: fill in the SEO description.
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- Render-blocking resourceshigh
0 blocking script(s) and 7 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- HTTP → HTTPS redirecthigh
http:// does not redirect to https://.
Fix: 301-redirect all http:// requests to https://.
- H1 headingcritical
2 H1 headings – one clear H1 is best practice.
Fix: Use one H1 that states the page topic with its main keyword.
On Squarespace: Select the main heading text and choose Heading 1 from the text style menu; use Heading 2 for the rest.
- Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- Trust pages (E-E-A-T)medium
Links found to about; missing contact and privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
- Anchor text qualitymedium
Same text used for different pages: “listen here”, “read more →”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to splitframeofreference.com…
Indexing & crawling 94%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap found at http://www.splitframeofreference.com/sitemap.xml with 339 URLs.
Declared in robots.txt.
This page is NOT listed in it.
Most recent lastmod: 2025-05-12.
- !
Canonical URLhigh
Canonical: http://www.splitframeofreference.com
Points to a DIFFERENT address – Google will probably index that one instead of this page.
The canonical uses http:// although the page is on https://.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- ✓
Redirectshigh
1 redirect before the page loaded.
https://splitframeofreference.com/ → https://www.splitframeofreference.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
splitframeofreference.com redirects to www.splitframeofreference.com.
Search snippet & sharing 67%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“SPLIT/FRAME OF REFERENCE”
About 293px of Google's ~580px desktop width.
- ✗
Meta descriptionhigh
No meta description – Google will pick text from the page.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
On Squarespace: Pages panel → gear icon on the page → SEO tab: fill in the SEO description.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en-US"
Content quality 77%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
483 words of main content (menus and footer excluded).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- ✓
Readabilitymedium
Flesch reading ease 50 (fairly easy), about 11 words per sentence.
- ✓
Topic focushigh
3 of 3 title keywords appear in the main content.
- !
H1 headingcritical
2 H1 headings – one clear H1 is best practice.
Fix: Use one H1 that states the page topic with its main keyword.
On Squarespace: Select the main heading text and choose Heading 1 from the text style menu; use Heading 2 for the rest.
- ✓
Heading structuremedium
5 headings for 483 words.
Levels are in order.
- ✗
Text-to-code ratiolow
2% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 50%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✗
Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✓
Freshness signalsmedium
The page shows when it was published or last updated.
- ✗
Trust pages (E-E-A-T)medium
Links found to about; missing contact and privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
1 JSON-LD block(s): WebSite.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 55%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
59 internal and 10 external links.
- ✗
Anchor text qualitymedium
Same text used for different pages: “listen here”, “read more →”.
3 link(s) with no text at all.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- !
Broken links (sample)high
Checked 12 internal link(s).
Broken: /@pastorgricel (404).
Fix: Fix or remove links that return errors, and update links that redirect.
- !
Internal links to http://medium
7 internal link(s) use http:// – each one goes through a redirect.
Fix: Update internal links to use https:// (or relative links).
Performance 47%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
265 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✓
HTML sizemedium
137 kB of HTML.
- ✓
Compressionmedium
Compressed with gzip.
- ✗
Render-blocking resourceshigh
0 blocking script(s) and 7 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
44 script tag(s); files loaded from 5 other domain(s): images.squarespace-cdn.com, use.typekit.net, assets.squarespace.com, definitions.sqspcdn.com, static1.squarespace.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
18 image(s).
14 without width/height – can cause layout shift (CLS).
11 image(s) after the first three aren't lazy-loaded.
4 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✗
Cachinglow
No Cache-Control header.
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 50%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✗
HTTP → HTTPS redirecthigh
http:// does not redirect to https://.
Fix: 301-redirect all http:// requests to https://.
- ✗
HSTSmedium
HSTS: max-age=0
max-age is under 6 months – browsers will forget it quickly.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✗
Security headerslow
Present: nosniff.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 70%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 18 images have alt text.
- ✗
Link nameslow
3 link(s) have no readable name for screen readers.
Fix: Add text or aria-label to icon-only links.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.