B+ · Good

Page SEO Inspection

https://brokerswatch.com/
Crawled 15 Nov, 10:05 UTC (16 hr ago)
HTTP 200 66 KB 846 ms TTFB
Download PDF

PDF export is a paid feature

A PDF of the full report, ready to send to a client or a colleague, comes with Basic at $19 a month and every plan above it, along with saved history. The report itself stays free to read.

See the plans
On-Page Checklist 75% Complete
Primary focus: Largest Contentful Paint is 7.8s (lab data), above the 2.5s target and in the poor range. Fix now →
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.

✓ 2100% · excellent
Live snippet simulation
Title width: 500px / 580px
B Brokers Watch brokerswatch.com
Unbiased Financial Company Directory — Brokers Watch

Research brokers, exchanges, and financial institutions with comprehensive, unbiased profiles.

Title tag 500px of 580px

The title length is well judged.

Rendered width

Desktop500px/ 580px
Mobile450px/ 920px

Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 52.

Meta description 94 characters

The meta description length is well judged.

Crawling & indexing

Whether search engines can reach, read and index this page at all.

i 1✓ 1794% · excellent
www and https versions 2 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.

https://www.brokerswatch.com/ → 302 → https://brokerswatch.com/ (temporary redirect)
http://www.brokerswatch.com/ → 302 → https://brokerswatch.com/ (temporary redirect)
How to fix
How to fix
Redirect each spelling straight to the final address with a 301 or 308.
HTTP status HTTP 200

The page returns 200 OK.

Redirect chain

The URL resolves without redirects.

Robots directives

No directive prevents indexing.

Canonical tag

The canonical correctly references this page.

https://brokerswatch.com/
Language

Language is declared as "en".

lang="en"
hreflang 3 found

3 hreflang annotations declared, including a self-reference.

Viewport

The viewport is configured for mobile.

width=device-width, initial-scale=1.0
Character encoding

The page declares UTF-8 encoding.

Favicon

A favicon is declared.

Mixed content

All resources load securely.

URL length 25 characters

The URL is 25 characters.

URL readability

The URL is clean and readable.

URL depth 0 levels deep

The page is 0 levels deep.

URL parameters

The URL has no query parameters.

robots.txt 1 KB

robots.txt is present and does not block crawling.

XML sitemap 9 URLs

A sitemap index is published, referencing 9 sitemaps.

Sitemap index referencing 9 sitemaps

Missing pages (404) HTTP 404

A page that does not exist returns HTTP 404, so search engines drop dead addresses.

Content & metadata

What the page says it is about, and how it reads.

i 2✓ 982% · good
Word count 484 Substantive
Headings 7 Structured
H1 tags 1 Exactly one
Text ratio 3.1% Text vs markup
Heading outline 7 headings
H1 Brokers Watch - Research Before You Invest
H2 Featured Companies
H2 Compare Firms Side by Side
H4 Directory
H4 Rankings & Compare
H4 Data & Safety
H4 Company & Resources
Heading hierarchy

The heading outline skips levels (h2 → h4).

h1: Brokers Watch - Research Before You Invest
  h2: Featured Companies
    h3: Apex Trader Funding
    h3: Barclays
    h3: Binance
    h3: Bitfinex
    h3: Bitstamp
    h3: BNP Paribas
    h3: Bybit
    h3: Capital.com
  h2: Compare Firms Side by Side
      h4: Directory
How to fix
How to fix
Descend one level at a time: h1, then h2, then h3.
Text-to-HTML ratio 3.1% text

Only 3.1% of the page is readable text; the rest is markup and script.

How to fix
How to fix
Move inline scripts and styles to external files, and remove unused markup.
Open Graph tags

Open Graph tags are present.

Twitter card

twitter:card is set to summary_large_image.

H1 tag

The page has exactly one h1.

Brokers Watch - Research Before You Invest
Content length 484 words

The page has roughly 484 words.

Table headers

No data tables on this page, so there are no columns to label.

Keyword placement

The page's prominent terms appear in its title, description or headings.

Where these terms appear

TermCountDensityTitleDescriptionHeadings
est82.10%✕✕✓
trading82.10%✕✕✕
offering71.84%✕✕✕
com71.84%✓✓✓
financial61.57%✓✓✕
Keyword repetition

No term is repeated unnaturally often.

Keyword cloud

The page's most frequent terms, from 381 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.

esttradingofferingcomfinancialwwwmarketscookiesbrokersexchangesregulationexchangebankingwatchunbiasedcomparefeescapitallistedbanksidefutureslargestspot0poorexchangefeaturedunitedessentialprivacysignresearchbeforeprofilesinstitutionsverifyprotectfirmregulatorbrokerfirmsbased
Share image 1920 × 1080 px

The share image loads and is 1920 × 1080 pixels, the right size and shape for a large card.

AI & answer readiness

Whether answer engines and AI overviews can extract and trust this page.

! 1i 5✓ 545% · needs work
AI crawlers 10/10 All allowed
Readable without JS No Needs JavaScript
Identity 1/2 Partly declared
Quotable signals 1/4 Schema, date, author, answers
Content needs JavaScript

Most of the page arrives with JavaScript: 202 words served, 484 after rendering.

served: 202 words
rendered: 484 words
How to fix
How to fix
A reader that does not run JavaScript sees roughly a third of this page. Serving the main content in the HTML makes it readable to every crawler, not only the ones that render.
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
How to fix
Open at least one section with a direct 40 to 60 word answer to the question its heading poses.
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
How to fix
<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.
Answer schema

No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.

How to fix
How to fix
Mark up question-and-answer content as FAQPage, or step-by-step content as HowTo.
Page subject

No structured data describes what this page is about.

Found: WebSite, Organization
None of these declare the page's subject.

2 types: WebSite, Organization

How to fix
How to fix
Describe the page with the type that fits it, Article for writing, Product for a product, FAQPage for questions and answers. Boilerplate like Organization and BreadcrumbList identifies the site, not the page.
Title needs JavaScript

The title changes after JavaScript runs.

served:   Brokers Watch – Independent Broker & Financial Company Reviews
rendered: Unbiased Financial Company Directory — Brokers Watch
How to fix
How to fix
Set the title in the HTML your server sends. A link preview, a social card and most answer engines read it there and never run the script that would change it.
Attribution

Attribution signals present: privacy policy, about page, contact page.

privacy policy, about page, contact page

Extractable structure 484 words

484 words across 15 headings, 6 lists and 0 tables.

Publisher identity

The page names who is behind it: Brokers Watch.

llms.txt for AI agents

llms.txt is published, giving AI agents a curated map of the site.

AI crawler access 10 checked

Every AI crawler checked is allowed to read this page.

Speed & delivery

What makes the page slow, and what the loading experience measures.

✕ 1! 4i 1✓ 754% · needs work
Rendered page
The page as it rendered on a mobile viewport during the performance test
Mobile, measured
The page as it rendered on a desktop viewport
Desktop, measured
LCP Poor
7.84s

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.

INP Good
71ms

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.

CLS Good
0.001

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.

FCP Good
1.68s

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.

TTFBNo data
n/a

Real-user response time

Target ≤ 800ms

Needs real-user data from Chrome UX Report

Time to first byte

Time to first byte is 846 ms, above the 800 ms Google treats as good.

How to fix
How to fix
Cache the response or reduce server work before the first byte.
Page weight 313 requests · 4.6 MB

The page loads 4.6 MB in 313 requests, among the heaviest tenth of the web. On a phone connection it takes many seconds before it is usable.

What loaded, by type

Type RequestsTransferred
image9of 6 declared3.0 MB
script211of 6 declared1.1 MB
other83349 KB
font271 KB
document629 KB
stylesheet227 KB

Of these, 105 requests (3.9 MB) come from third-party domains.

How to fix
How to fix
Remove scripts that are not needed for the first screen, lazy-load below-the-fold media, and serve images in a modern format at display size.
Third-party services 9 services · 3.8 MB

9 third-party services account for 83% of what this page downloads, 3.8 MB and 238ms of main-thread time.

Third-party services

Service TransferredMain thread
supabase.co3.2 MBunder 1ms
Google/Doubleclick Ads280 KB115ms
Google Tag Manager192 KB94ms
Google Fonts72 KBunder 1ms
adtrafficquality.google29 KB11ms
Cloudflare10 KB17ms
ipapi.co3 KBunder 1ms
Other Google APIs/SDKs2 KB1ms
Google Analytics1 KBunder 1ms

0.2s of main-thread time

How to fix
How to fix
Audit what each service earns its weight doing, remove any that duplicate another, and load the rest after the page is interactive.
Browser caching 2.4 MB re-downloaded

9 files have cache lifetimes short enough that returning visitors download 2.4 MB again.

Short cache lifetimes

FileCache lifetimeSize
psqrorwdvanvwrqzevpq.supabase.co/jobwatch.webp1h2.8 MB
pagead2.googlesyndication.com/show_ads_impl_fy2021.js14d167 KB
psqrorwdvanvwrqzevpq.supabase.co/mobile-logo.webp1h84 KB
psqrorwdvanvwrqzevpq.supabase.co/mobile-logo.webp1h84 KB
pagead2.googlesyndication.com/rum_fy2021.js14d24 KB
psqrorwdvanvwrqzevpq.supabase.co/logo.webp1h21 KB
psqrorwdvanvwrqzevpq.supabase.co/logo.webp1h21 KB
static.cloudflareinsights.com/…823e78c4301a35b7e07294d873017920888140921d10 KB
ikmecxkcmikymukbmfsa.supabase.co/capital-com.png1h5 KB
How to fix
How to fix
Serve static assets with a long max-age and a content hash in the filename, so a new version gets a new URL rather than a short expiry.
Render-blocking resources 3 found

3 resources in <head> block the first paint, delaying when anything appears on screen.

stylesheet: https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&family=Space+Grotesk:wght@500;600;700&display=swap
stylesheet: /assets/styles-CYFUC2e8.css
script: https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202611100101/show_ads_impl.js
How to fix
How to fix
Add defer to scripts, inline critical CSS, and load the rest asynchronously.
HTML size 66 KB

The HTML document is 66 KB.

Deprecated tags

No deprecated HTML tags are used.

Inline styles 23 found

23 inline style attributes.

Compression

The response is compressed with zstd.

Content-Encoding: zstd

Security

Transport security, reputation and the response headers that protect visitors.

! 1i 3✓ 969% · fair
Clickjacking protection

Nothing prevents this page being embedded in a frame, which allows clickjacking.

How to fix
How to fix
Content-Security-Policy: frame-ancestors 'self'
Content Security Policy

No Content-Security-Policy, the main defence against cross-site scripting.

How to fix
How to fix
Content-Security-Policy: default-src 'self'
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
How to fix
Permissions-Policy: camera=(), microphone=(), geolocation=()
security.txt

No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.

https://brokerswatch.com/.well-known/security.txt
How to fix
How to fix
Publish /.well-known/security.txt with a Contact: line (an email address or a form) and an Expires: date.
Email addresses in the page

No email addresses are written into the page for harvesting bots to collect.

HSTS

HTTPS is enforced with Strict-Transport-Security.

max-age=31536000; includeSubDomains
MIME sniffing

MIME sniffing is disabled.

Referrer policy

Referrer-Policy is "strict-origin-when-cross-origin".

strict-origin-when-cross-origin
Cookie flags

The cookie the page sets carries Secure, HttpOnly and SameSite.

Version disclosure

No software versions are disclosed in headers or the page.

TLS certificate 37 days left

The TLS certificate is valid for another 37 days, issued by Google Trust Services.

37 days remaining
Google Web Risk

Not listed by Google Web Risk for malware, phishing or unwanted software.

TLS version TLS 1.3

Connections use TLS 1.3.

Server & domain

The server and the domain behind the page: protocol, network, registration and email records.

i 1✓ 788% · good
DMARC policy

The DMARC policy for brokerswatch.com is p=none, which collects reports but does not stop mail that spoofs the domain.

v=DMARC1; p=none; rua=mailto:[email protected]
How to fix
How to fix
Once the reports show only your own services sending, move to p=quarantine and then p=reject.
HTTP/2 HTTP/2

Served over HTTP/2, which loads a page's files in parallel over one connection.

HTTP/3 HTTP/3

Announces HTTP/3, which browsers switch to on a later visit for faster connections on poor networks.

CDN Cloudflare

Served through Cloudflare, a CDN, so visitors get the page from a server near them.

Domain expiry 1096 days left

brokerswatch.com is registered until 16 Nov 2029 with Wild West Domains, LLC.

1096 days remaining
Domain age 15 years old

brokerswatch.com was registered on 16 Nov 2010, 15 years ago. Age is not a ranking factor, but an established name is one buyers and partners look for.

IPv6

brokerswatch.com has an IPv6 address, so IPv6-only networks reach it directly.

SPF record

brokerswatch.com publishes an SPF record: v=spf1 include:spf.titan.email ~all

ads.txt

No ad network loads on this page, so ads.txt is not needed.

Links, media & schema

Links, images and structured data.

! 2✓ 1083% · good
Social share preview From this page's Open Graph tags
Image dimensions 5 found

5 images have no width and height, so the page shifts as they load (hurting CLS).

Shown as 4 unique sources; the counts show how often each repeats.

# / lineImage source
#1 L27https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/mobile-logo.webp?t=1790511020057&v=frjfoq01<img src="https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/mobile-logo.webp?t=1790511020057&amp;v=frjfoq01" alt="Brokers Watch" class="h-7 w-auto object-contain">
#2 L27https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/logo.webp?t=1790083965726&v=frjfoq01 ×2<img src="https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/logo.webp?t=1790083965726&amp;v=frjfoq01" alt="Brokers Watch" class="h-8 w-auto object-contain">
JShttps://ikmecxkcmikymukbmfsa.supabase.co/storage/v1/object/public/entity-media/companies/capital-com.png?t=1776860142633<img class="aspect-square h-full w-full object-contain p-0.5" alt="Capital.com logo" src="https://ikmecxkcmikymukbmfsa.supabase.co/storage/v1/object/public/entity-media/companies/capital-com.png?t=1776860142633">
#4 L27https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/logo.webp?t=1790083965726<img src="https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/logo.webp?t=1790083965726" alt="Brokers Watch" loading="lazy" decoding="async" class="h-9 w-auto max-w-[200px] object-contain">
How to fix
How to fix
<img src="…" width="800" height="600">, the browser reserves the space before decoding.
Responsive images 6 found

6 large images are served at one fixed size, so phones download desktop-sized files.

Shown as 5 unique sources; the counts show how often each repeats.

# / lineImage source
#1 L27https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/mobile-logo.webp?t=1790511020057&v=frjfoq01<img src="https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/mobile-logo.webp?t=1790511020057&amp;v=frjfoq01" alt="Brokers Watch" class="h-7 w-auto object-contain">
#2 L27https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/logo.webp?t=1790083965726&v=frjfoq01 ×2<img src="https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/logo.webp?t=1790083965726&amp;v=frjfoq01" alt="Brokers Watch" class="h-8 w-auto object-contain">
JShttps://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/ads/jobwatch.webp?t=1793286147990<img alt="Jobwatch" loading="lazy" decoding="async" width="1200" height="200" class="mx-auto block h-auto w-auto max-w-full" src="https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/ads/jobwatch.webp?t=1793286147990">
JShttps://ikmecxkcmikymukbmfsa.supabase.co/storage/v1/object/public/entity-media/companies/capital-com.png?t=1776860142633<img class="aspect-square h-full w-full object-contain p-0.5" alt="Capital.com logo" src="https://ikmecxkcmikymukbmfsa.supabase.co/storage/v1/object/public/entity-media/companies/capital-com.png?t=1776860142633">
#5 L27https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/logo.webp?t=1790083965726<img src="https://psqrorwdvanvwrqzevpq.supabase.co/storage/v1/object/public/entity-media/site/logo.webp?t=1790083965726" alt="Brokers Watch" loading="lazy" decoding="async" class="h-9 w-auto max-w-[200px] object-contain">
How to fix
How to fix
<img src="hero.jpg" srcset="hero-400.jpg 400w, hero-800.jpg 800w" sizes="(max-width: 600px) 400px, 800px">
Structured data

Structured data is valid: WebSite, Organization.

WebSite, Organization

2 types: WebSite, Organization

Rich result eligibility

Eligible for rich results via Organization.

Organization

1 type: Organization

Link distribution 91 resources

88 internal and 3 external links.

88 internal, 3 external

88 internal, 3 external

Anchor text

Anchor text describes its destinations.

Link rel attributes

Outbound link rel attributes look appropriate.

In-page anchors

In-page anchors resolve to real targets.

Image alt text

All images carry an alt attribute.

Image formats

No heavy legacy image formats found.

5 already in a modern format

Image loading

Image loading strategy looks sound.

Broken links 25 checked

All 25 checked links resolve.

What to fix first

Ranked by impact against effort, the top of this list buys the most for the least work.

1
✕ Critical Largest Contentful Paint is 7.8s (lab data), above the 2.5s target and in the poor range.
Optimise the hero image, remove render-blocking CSS and JS, and improve server response time.
moderate
2
! Recommended The page loads 4.6 MB in 313 requests, among the heaviest tenth of the web. On a phone connection it takes many seconds before it is usable.
Remove scripts that are not needed for the first screen, lazy-load below-the-fold media, and serve images in a modern format at display size.
involved
3
! Recommended 5 images have no width and height, so the page shifts as they load (hurting CLS).
<img src="…" width="800" height="600">, the browser reserves the space before decoding.
quick fix
4
! Recommended 9 third-party services account for 83% of what this page downloads, 3.8 MB and 238ms of main-thread time.
Audit what each service earns its weight doing, remove any that duplicate another, and load the rest after the page is interactive.
moderate
5
! Recommended Nothing prevents this page being embedded in a frame, which allows clickjacking.
Content-Security-Policy: frame-ancestors 'self'
quick fix
6
! Recommended 9 files have cache lifetimes short enough that returning visitors download 2.4 MB again.
Serve static assets with a long max-age and a content hash in the filename, so a new version gets a new URL rather than a short expiry.
quick fix
7
! Recommended 6 large images are served at one fixed size, so phones download desktop-sized files.
<img src="hero.jpg" srcset="hero-400.jpg 400w, hero-800.jpg 800w" sizes="(max-width: 600px) 400px, 800px">
moderate
8
! Recommended Time to first byte is 846 ms, above the 800 ms Google treats as good.
Cache the response or reduce server work before the first byte.
moderate
9
! Recommended Most of the page arrives with JavaScript: 202 words served, 484 after rendering.
A reader that does not run JavaScript sees roughly a third of this page. Serving the main content in the HTML makes it readable to every crawler, not only the ones that render.
involved
10
· Notice 3 resources in <head> block the first paint, delaying when anything appears on screen.
Add defer to scripts, inline critical CSS, and load the rest asynchronously.
moderate
11
· Notice The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.
<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.
quick fix
12
· Notice No structured data describes what this page is about.
Describe the page with the type that fits it, Article for writing, Product for a product, FAQPage for questions and answers. Boilerplate like Organization and BreadcrumbList identifies the site, not the page.
quick fix

Score breakdown

How each area scored. Categories that could not be measured are excluded rather than counted as zero.

Indexability & Crawling40 checks · 6 issues
89
On-Page Content & Structure23 checks · 8 issues
84
Core Web Vitals13 checks · 6 issues
52
Schema & Rich Snippets2 checks · 0 issues
100
Media & Links10 checks · 2 issues
91
Overall scoreGrade B+ · 66/89 passed
82