Back to Home

fbn.com SEO Analysis

fbn.com scores 74/100 for SEO, 38/100 for performance, and 75/100 for AI crawler readability as of Mar 26, 2026.

https://fbn.com
15 checks
36 issues
Mar 26, 2026
https://fbn.com
Desktop preview
Desktop
Mobile preview
Mobile
Score Analysis
LIVE
66OF 100
Needs Work
74
SEO
38
Perf
75
AI
Page Title

ERROR: The request could not be satisfied

Google Search Preview|How your page appears in search results
SERP Score
0/ 100
Needs Work
fbn.com
https://fbn.com
ERROR: The request could not be satisfied
No meta description found
Snippet Quality
Title Length41 chars
03060 optimal90
Description Length0 chars
070160 optimal240
Power Word
CTA
URL Readable
HTTPS
No Truncation
Recommendations4 found
infoTitle lacks CTR-boosting power words
Consider adding words like "free", "guide", "best" to improve click-through rate
criticalMissing meta description
Add <meta name="description" content="..."> with 150-160 chars
warningMissing viewport meta tag
Add <meta name="viewport" content="width=device-width, initial-scale=1">
infoMissing lang attribute on <html>
Add lang="en" (or your language) to <html>
Performance Report|Google PageSpeed Insights
Lighthouse v13.0.1Mar 26, 2026, 09:41 PM
Status403ERROR
Load Time0.50sFAST
HTML Size1 KBOK
CompressionNoneOFF
HTTPSSecureSECURE
Render-Block0 scriptsNONE
0/ 100
Poor
LCPPOOR
12.1 s
Largest Contentful Paint
FCPNEEDS WORK
2.4 s
First Contentful Paint
TBTPOOR
1,760 ms
Total Blocking Time
CLSGOOD
0
Cumulative Layout Shift
SIPOOR
7.1 s
Speed Index
TTFBGOOD
Root document took 30 ms
Time to First Byte
FIDPOOR
490 ms
First Input Delay
Page Load FilmstripVisual timeline of how your page renders
Frame at 0.4s
0.4s
Frame at 0.8s
0.8s
Frame at 1.2s
1.2s
Frame at 1.6s
1.6s
Frame at 2.0s
2.0s
Frame at 2.4s
2.4s
Frame at 2.8s
2.8s
Frame at 3.2s
3.2s
Issues Found12 found
criticalLargest Contentful Paint: 12.1 s (poor)high
How to fixOptimize images, preload LCP element, reduce server response time. Target < 2.5s
What this meansLCP measures when the largest visible element finishes rendering.
SEO ImpactSlow LCP increases bounce rate and hurts Core Web Vitals ranking signal.
criticalTotal Blocking Time: 1,760 ms (poor)high
How to fixBreak up long tasks, defer non-critical JavaScript, use web workers. Target < 200ms
What this meansTBT measures total time the main thread was blocked. It's a lab proxy for INP.
SEO ImpactHigh TBT means the page feels unresponsive. This directly impacts INP, a Core Web Vital.
warningSpeed Index: 7.1 s (poor)medium
How to fixOptimize critical rendering path, reduce main-thread work. Target < 3.4s
What this meansSpeed Index measures how quickly content is visually displayed during page load.
SEO ImpactA high Speed Index means the page appears to load slowly.
warningAvoid multiple page redirects - Est savings of 780 ms (potential savings: 780ms)
How to fixRedirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
warningReduce unused JavaScript - Est savings of 426 KiB (potential savings: 450ms) / 426 KB
How to fixReduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
infoReduce unused CSS - Est savings of 12 KiB (potential savings: 12 KB)
How to fixReduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
infoAvoid enormous network payloads - Total size was 3,530 KiB
How to fixLarge network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
infoReduce JavaScript execution time - 3.8 s
How to fixConsider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
infoMinimize main-thread work - 5.3 s
How to fixConsider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
infoImage elements do not have explicit `width` and `height`
How to fixSet an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
criticalHTTP status 403
How to fixFix the server response
warningNo gzip/brotli compression
How to fixEnable gzip or brotli compression
OpportunitiesPotential savings to improve load time
Avoid multiple page redirectsEst savings of 780 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
0.8s potential savings
Reduce unused JavaScriptEst savings of 426 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
0.5s potential savings 426 KB transferable
Reduce unused CSSEst savings of 12 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
12 KB transferable
Avoid enormous network payloadsTotal size was 3,530 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
DiagnosticsAdditional performance insights
Reduce JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
3.8 s
Minimize main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
5.3 s
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
LCP breakdown
Diagnostics
Duplicated JavaScript
Screenshot Thumbnails
Minify JavaScript
Optimize viewport for mobile
Avoid long main-thread tasks
Resources Summary
Minify CSS
Layout shift culprits
Final Screenshot
3rd parties
Server Backend Latencies
Avoid large layout shifts
Initial server response time was short
Network Requests
Font display
Tasks
Forced reflow
Network Round Trip Times
Cumulative Layout Shift
Optimize DOM size
User Timing marks and measures
Metrics
Script Treemap Data
Heading Structure|Content hierarchy and heading tags
100 / 100
H1
1
ideal: 1
H2
1
ideal: 2+
H3
0
ideal: optional
H4
0
ideal: optional
Heading Hierarchy2 total
H1403 ERROR
H2The request could not be satisfied.
Structured Data|Schema markup, Open Graph and Twitter Cards
35 / 100
JSON-LD Schema
Not found
Open Graph
Not found
Twitter Cards
Not found
Microdata
Not found
Recommendations3
criticalNo JSON-LD structured data found
Add JSON-LD schema markup (e.g., WebPage, Organization, Article)
criticalMissing Open Graph tags: og:title, og:description, og:image, og:url, og:type
Add OG meta tags for social sharing
warningNo Twitter Card meta tags
Add twitter:card, twitter:title, twitter:description meta tags
Image Optimization|Alt text, lazy loading and dimensions
80 / 100
Total Images
0
Missing Alt Text
0
Missing Dimensions
0
Lazy Loaded
0%
0 of 0 images
Recommendations1
infoNo images found
Consider adding relevant images
Indexability|Robots, canonical and sitemap
90 / 100
Canonical URL
Missing
Noindex
Allowed
Robots.txt
Found
Sitemap
Found
https://fbn.com/sitemap.xml
Crawl Directives
Meta RobotsNot set
X-Robots-TagNot set
GooglebotNot set
NofollowNo — links followed
CanonicalNot set
Page URLhttps://fbn.com
Recommendations1
warningNo canonical tag found
Add <link rel="canonical"> pointing to the preferred URL
Content Structure|Content quality and semantic HTML
55 / 100
Word Count
84
Paragraphs
0
All good length
Lists
0
Words per Heading
42
Ideal: 100-300
Title vs H1 Alignment2000% similar
TITLE TAG
ERROR: The request could not be satisfied
H1 TAG
403 ERROR
Semantic HTML Elements
<main>
<article>
<nav>
<header>
<footer>
Recommendations4
warningLow word count (84)
Aim for at least 300+ words
warningTitle and H1 have low similarity (20%)
Align your <title> and <h1> to reinforce the main topic
infoH2 headings don't relate to the main H1 topic
Ensure H2s support the main topic for better coherence
warningFew semantic HTML5 elements used
Use <main>, <article>, <nav>, <header>, <footer>, <section>
AI Readability|How easily AI models can process your content
90 / 100
65Flesch
Reading Level
Easy
AI-friendly
Total Words
84
Sentences
6
Avg Sentence Length
14 words
Vocabulary Richness
73%
61 unique words
Recommendations1
infoFirst paragraph is too short for AI summarization
Make the first paragraph a comprehensive summary (30-50 words)
AI Citation Potential|How likely AI will quote your content
100 / 100
Named Entities
3
357% density
FAQ Patterns
0
No FAQ Schema
Citations
0
Lists & Tables
0 items, 0 tables
Top Named Entities
CloudFront2The1Request1
Content Freshness|Date signals and cache headers
75 / 100
Date Signals
None
No date signals found on page
Cache Control
Not set
ETag
Not set
Date Signals
Last-Modified HeaderNot found
Published DateNot found
Modified DateNot found
Recommendations2
warningNo datePublished or dateModified in structured data
Add datePublished and dateModified to your JSON-LD schema.
infoNo date/time signals found anywhere on page
Add <time datetime="..."> elements or schema dates to help AI assess content freshness
Security Headers|HTTP security headers analysis
40 / 100
Content-Security-Policy
Prevents XSS and injection attacks
MISSING
Strict-Transport-Security
Forces HTTPS connections
max-age=31536000; includeSubDomains; preload
SET
X-Frame-Options
Prevents clickjacking attacks
MISSING
X-Content-Type-Options
Prevents MIME-type sniffing
MISSING
Referrer-Policy
Controls referrer information
MISSING
Permissions-Policy
Controls browser features
MISSING
Recommendations5
criticalMissing Content-Security-Policy header
Add Content-Security-Policy header to prevent XSS and data injection attacks
warningMissing X-Frame-Options header
Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
warningMissing X-Content-Type-Options header
Add X-Content-Type-Options: nosniff to prevent MIME-type sniffing
infoMissing Referrer-Policy header
Add Referrer-Policy header (e.g., strict-origin-when-cross-origin)
Trust Signals|Essential trust-building pages
75 / 100
Contact Page
MISSING
A contact page builds trust with visitors and search engines
About Page
MISSING
An about page establishes credibility and expertise
Privacy Policy
MISSING
Required for compliance and builds user trust
Terms of Service
MISSING
Protects both the site owner and users
Recommendations2
warningMissing trust pages: contact, about, privacy, terms
Add links to Contact, About, Privacy Policy, and Terms pages.
infoNo author attribution found
Add author information via schema markup or rel="author" for E-E-A-T signals
Tech Stack|1 technologies detected
55 / 100
CDN1
🌩️
CloudFront
Server: CloudFront
header