Site Report: legacy.reactjs.org (old docs, kept online)
React documentation (public)
2026-10-23 13:26 / 2026-10-23_131318
Crawl data: 2026-10-23_131318
Executive Summary
At Risk

93 of 100 pages have at least one priority problem. Most trace back to a missing meta description.

Health: At Risk, based on 100 pages crawled from legacy.reactjs.org (old docs, kept online).

Nothing was set aside before analysis.

Note: Only the first 100 pages were crawled; counts describe that sample.

What we found
  1. All 90 pages have no meta description, leaving search engines to choose snippet text on their own. See evidence(Findings tab)
    e.g. /, /acknowledgements.html, /blog/2015/12/18/react-components-elements-and-instances.html and 87 more
  2. All 90 pages carry no structured data (JSON-LD). See evidence(Findings tab)
    e.g. /, /acknowledgements.html, /blog/2015/12/18/react-components-elements-and-instances.html and 87 more
  3. 93 of 229 images have no alt text. See evidence(Findings tab)
  4. The page HTML still loads Universal Analytics. Universal Analytics stopped processing data on July 1, 2023. See evidence(Dashboard tab)
  5. No XML sitemap was found at the standard addresses, and robots.txt declares none. See evidence(Dashboard tab)
Fix first
  1. Add meta descriptions (90 pages) See evidence(Findings tab)
  2. Add structured data (JSON-LD) to key pages (90 pages) See evidence(Findings tab)
  3. Add alt text to images (93 images) See evidence(Findings tab)

Working well: Internal links are 100% HTTPS, pages average 1,694 words, and the average response time is 81 ms. 88 of 90 crawled pages send signals that allow indexing. Every host form reaches https://legacy.reactjs.org in one permanent redirect, and deep links keep their path.

100
Pages Crawled
732
Total Issues
96
Pre-Launch Priority
413
Recommended
2156
Implemented Well
At Risk
Site Health
Site Health Metrics

Cross-page analysis of SEO fundamentals across the site.

Unique Titles 97.8%
1 duplicate group
Schema Coverage 0.0%
Pages with JSON-LD structured data
Alt Text Coverage 59.4%
136 of 229 images
HTTPS Links 100.0%
Internal links using secure protocol
Avg Word Count 1694
15 thin pages (<300 words)
Avg Response 81ms
Server response time average
Thin Pages 15
15.0% of pages under 300 words
Orphan Pages 0
Pages with no inbound internal links
SEO Strategy & Reach
25/100
Weak
📍 Location: ,
🗺 Service Area: Unknown
25% -- Weak
Geographic Reach
0/20
Scoring Methodology ▶
Sub-Score Points What Was Measured
Geo Page Coverage 0/4 No geo-targeted pages found
Market-Relative Coverage 0/4 0 geo pages (unknown market expects 8+)
Content Localization 0/4 no geo pages to assess
NAP & Local Schema 0/4 No phone or LocalBusiness schema found
Service Area Strategy 0/4 No geographic targeting strategy detected
Scoring Criteria:
  • Geo Page Coverage: Raw count of dedicated geo-targeted pages. 0 pages = 0, 1-3 = 1, 4-7 = 2, 8-15 = 3, 16+ = 4.
  • Market-Relative Coverage: Geo pages relative to market size. is a unknown market (expects 8+ pages for full score). Thresholds: <10% = 0, 10-29% = 1, 30-59% = 2, 60-99% = 3, 100%+ = 4.
  • Content Localization: Measures whether geo pages contain genuine local content or are template copies with only city names swapped. Additive scoring: +1 if titles >80% unique, +1 if descriptions >50% unique, +1 if headings mention city names, +1 if word counts vary >15%.
  • NAP & Local Schema: Business identity signals. No NAP = 0, phone only = 1, LocalBusiness schema but inconsistent NAP = 2, consistent NAP + schema = 3, consistent NAP + schema ON geo pages = 4.
  • Service Area Strategy: How strategic is the geographic targeting? No strategy = 0, only listing page = 1, <30% suburb coverage = 2, 30-60% = 3, >60% = 4. Multi-state presence can boost by +1.
Service Depth
0/20
Scoring Methodology ▶
Sub-Score Points What Was Measured
Service pages 0/None 0 pages
Content-rich (300+ words) 0/0 0 of 0
With review schema 0/0 0 of 0
Content Authority
14/20
Scoring Methodology ▶
Sub-Score Points What Was Measured
Avg word count 4/4 1694 words (content pages)
Meta description coverage 0/4 0% (0/100)
Title uniqueness 4/4 97.8% unique
H1 quality 4/4 93% of pages have exactly 1 H1
Content uniqueness 2/4 2 near-duplicate group(s)
Technical Foundation
7/20
Scoring Methodology ▶
Sub-Score Points What Was Measured
Sitemap coverage 0/4 0% (0/100)
Schema coverage 0/4 0.0% coverage
Meta tag coverage 0/4 0% have title+desc+canonical
Indexation health 4/4 0 noindex, 0 bad canonical
Performance & security 3/4 HTTPS: 93%, avg response: 81ms, HSTS: yes
Competitive Positioning
4/20
Scoring Methodology ▶
Sub-Score Points What Was Measured
Brand consistency 0/4 0% of titles
Review signals 0/4 0 pages, 0 reviews
Local business signals 0/4 0 pages, 0 complete
Internal linking 4/4 avg 63.4 links/page
Differentiated content 0/4 0 schema types, FAQ: no
What does this score mean? ▶

What the Strategy & Reach Score Means for Publishers

For a blog, documentation site or publication, content is the product, so the score reads a little differently than it does for a business site:

Topic depth. The Service Depth dimension counts dedicated, substantial pages for each topic, guide or section. Pillar pages that cover a subject thoroughly and link out to related articles rank better, and keep readers longer, than a flat stream of posts.

Content authority. Unique titles and descriptions, one clear H1 per page, substantial articles and no near-duplicate pages (tag archives, printer versions, syndicated copies) are the core of a publisher's search visibility.

Trust signals. A consistent brand in page titles, Organization and Article structured data, author and about pages, FAQ markup where it fits and rich internal linking between related pieces help search engines and readers judge the content as credible.

Technical foundation. An XML sitemap that covers every article, canonical URLs on syndicated or paginated content, noindex used only where intended, HTTPS and fast pages make sure new work is found and indexed quickly.

Geographic reach matters mainly to local news and regional publications; for other publishers it is informational.

Together, these show whether a site is built to earn search traffic across its topics, or relies on visitors who already know where to look.

Issue Breakdown by Severity
Severity Count Description
Implemented Well 2207 SEO best practices properly implemented. Great work!
Pre-Launch Priority 96 Issues that directly impact SEO rankings or user experience and should be addressed before launch.
Recommended 413 Improvements that would strengthen the site's search presence and overall quality.
Informational 223 Minor observations and nice-to-have improvements for reference.
Site-Level Checks

5 checks: 2 pass, 2 warn, 1 info. Based on what Webtrace can see from outside the site (12 extra requests).

Status Check Finding
Pass One canonical address
Every host form reaches https://legacy.reactjs.org in one permanent redirect, and deep links keep their path.
https://legacy.reactjs.org/ (200); HSTS on
  • Pass http://legacy.reactjs.org reaches https://legacy.reactjs.org in one permanent redirect.
    http://legacy.reactjs.org/ -> 308 -> https://legacy.reactjs.org/ (200)
  • Pass Deep links on http://legacy.reactjs.org keep their path.
    http://legacy.reactjs.org/versions -> 308 -> https://legacy.reactjs.org/versions (200)
Pass Unknown URLs return 404
An address that does not exist answers 404 (Not Found).
https://legacy.reactjs.org/webtrace-soft-404-check-195fe77bdac6/ -> 308 -> https://legacy.reactjs.org/webtrace-soft-404-check-195fe77bdac6 (404)
  • Pass An address that does not exist answers 404 (Not Found).
    https://legacy.reactjs.org/webtrace-soft-404-check-195fe77bdac6/ -> 308 -> https://legacy.reactjs.org/webtrace-soft-404-check-195fe77bdac6 (404)
Warn Discovery files (robots.txt and sitemap)
No XML sitemap was found at the standard addresses, and robots.txt declares none.
https://legacy.reactjs.org/robots.txt (200, 33 bytes, 0 Sitemap lines)
  • Pass robots.txt loads (200).
    https://legacy.reactjs.org/robots.txt (200, 33 bytes, 0 Sitemap lines)
  • Warn No XML sitemap was found at the standard addresses, and robots.txt declares none.
    https://legacy.reactjs.org/sitemap.xml (404)
    https://legacy.reactjs.org/sitemap_index.xml (404)
    https://legacy.reactjs.org/wp-sitemap.xml (404)
What to do: Publish an XML sitemap and declare it in robots.txt with a Sitemap: line.
Warn Analytics tags
The page HTML still loads Universal Analytics. Universal Analytics stopped processing data on July 1, 2023.
UA-41298772-1 (Universal Analytics) 100% (90/90)
  • Pass UA-41298772-1 (Universal Analytics) is on 100% (90/90) of the crawled pages.
  • Warn The page HTML still loads Universal Analytics. Universal Analytics stopped processing data on July 1, 2023.
What to do: Remove the Universal Analytics tag; measure with Google Analytics 4.
Info Ownership verification tags
The homepage carries no verification meta tags.
  • Info The homepage carries no verification meta tags.
    Search Console may also be verified by a DNS record, an HTML file, Google Analytics or Tag Manager, which page HTML does not show.

What these checks cannot see: Search Console ownership verified by DNS record, HTML file, Google Analytics or Tag Manager; analytics sent from the server or added later by JavaScript or a consent tool; redirects that depend on cookies, location or the visitor's browser; anything behind a login. Probe requests identify themselves as WebtraceBot and follow robots.txt.

Page-by-Page Audit (100 pages)
URL Title Status Words Issues Health Indexable
▶blog React - Page Not Found 404 106 1 At Risk --
  1. Pre-Launch Priority MISSING: Page not found -- this URL returns a 404 error
    This URL returns a 404 error. The page needs to be created or the URL needs to be redirected.
▶docs/more-about-refs.html React - Page Not Found 404 106 1 At Risk --
  1. Pre-Launch Priority MISSING: Page not found -- this URL returns a 404 error
    This URL returns a 404 error. The page needs to be created or the URL needs to be redirected.
▶docs/webcomponents.html React - Page Not Found 404 106 1 At Risk --
  1. Pre-Launch Priority MISSING: Page not found -- this URL returns a 404 error
    This URL returns a 404 error. The page needs to be created or the URL needs to be redirected.
▶blog/2017/04/07/react-v15.5.0.html React v15.5.0 – React Blog 200 1616 10 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Recommended LINKS: 1 mixed-content links (HTTP on HTTPS page)
    Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings.
  8. Informational META: Title too short (26 chars, recommended min 30)
    The title tag is only 26 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  9. Informational CONTENT: Very low text-to-HTML ratio (8.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  10. Informational PERFORMANCE: Large page (126 KB, recommended <100KB)
    The page weighs 126 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/code-splitting.html Code-Splitting – React 200 1976 10 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Recommended LINKS: 1 mixed-content links (HTTP on HTTPS page)
    Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings.
  8. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  9. Informational CONTENT: Very low text-to-HTML ratio (7.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  10. Informational PERFORMANCE: Large page (152 KB, recommended <100KB)
    The page weighs 152 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/faq-structure.html File Structure – React 200 730 10 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Recommended LINKS: 1 mixed-content links (HTTP on HTTPS page)
    Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings.
  8. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  9. Informational CONTENT: Very low text-to-HTML ratio (4.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  10. Informational PERFORMANCE: Large page (111 KB, recommended <100KB)
    The page weighs 111 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/testing-recipes.html Testing Recipes – React 200 3651 10 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Recommended LINKS: 1 mixed-content links (HTTP on HTTPS page)
    Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings.
  8. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  9. Informational CONTENT: Very low text-to-HTML ratio (8.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  10. Informational PERFORMANCE: Large page (212 KB, recommended <100KB)
    The page weighs 212 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/cdn-links.html CDN Links – React 200 484 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 3 images missing alt text
    Some images are missing alt text (1 of 3 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 2 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (2 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (17 chars, recommended min 30)
    The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (2.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (116 KB, recommended <100KB)
    The page weighs 116 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/codebase-overview.html Codebase Overview – React 200 1457 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (6.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (131 KB, recommended <100KB)
    The page weighs 131 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/conditional-rendering.html Conditional Rendering – React 200 1592 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (29 chars, recommended min 30)
    The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (5.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (150 KB, recommended <100KB)
    The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/faq-ajax.html AJAX and APIs – React 200 887 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (21 chars, recommended min 30)
    The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (3.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (125 KB, recommended <100KB)
    The page weighs 125 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/faq-functions.html Passing Functions to Components – React 200 2189 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Recommended LINKS: 1 mixed-content links (HTTP on HTTPS page)
    Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings.
  8. Informational CONTENT: Very low text-to-HTML ratio (6.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (165 KB, recommended <100KB)
    The page weighs 165 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/faq-state.html Component State – React 200 980 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (5.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (120 KB, recommended <100KB)
    The page weighs 120 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/faq-styling.html Styling and CSS – React 200 517 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (2.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (112 KB, recommended <100KB)
    The page weighs 112 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/faq-versioning.html Versioning Policy – React 200 1247 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (6.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (115 KB, recommended <100KB)
    The page weighs 115 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/hooks-intro.html Introducing Hooks – React 200 1806 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 iframes without title attribute
    Some iframes lack title attributes (1 iframes without title attribute). Adding titles improves accessibility by helping screen readers describe embedded content.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (8.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (128 KB, recommended <100KB)
    The page weighs 128 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/hooks-overview.html Hooks at a Glance – React 200 2258 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (8.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (150 KB, recommended <100KB)
    The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/hooks-rules.html Rules of Hooks – React 200 1290 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (5.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (126 KB, recommended <100KB)
    The page weighs 126 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/how-to-contribute.html How to Contribute – React 200 2042 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (8.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (136 KB, recommended <100KB)
    The page weighs 136 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/introducing-jsx.html Introducing JSX – React 200 1279 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (5.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (132 KB, recommended <100KB)
    The page weighs 132 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/lists-and-keys.html Lists and Keys – React 200 1876 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (5.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (157 KB, recommended <100KB)
    The page weighs 157 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/refs-and-the-dom.html Refs and the DOM – React 200 2171 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (24 chars, recommended min 30)
    The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (7.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (149 KB, recommended <100KB)
    The page weighs 149 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/strict-mode.html Strict Mode – React 200 1996 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 4 images missing alt text
    Some images are missing alt text (1 of 4 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 3 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (3 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (19 chars, recommended min 30)
    The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (9.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (136 KB, recommended <100KB)
    The page weighs 136 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/testing-environments.html Testing Environments – React 200 1125 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (5.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (119 KB, recommended <100KB)
    The page weighs 119 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/testing.html Testing Overview – React 200 665 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (24 chars, recommended min 30)
    The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (3.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (113 KB, recommended <100KB)
    The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶redirect-to-codepen/reconciliation/index-used-as-key 200 79 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Title tag
    Consider adding a title tag to help search engines understand this page's content and improve its appearance in search results.
  2. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  3. Recommended MISSING: Canonical tag
    A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs.
  4. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  5. Recommended THIN CONTENT: Only 79 words
    This page has limited text content (79 words). Expanding the content could improve its relevance for search queries and provide more value to visitors.
  6. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  7. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  8. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  9. Informational CONTENT: Very low text-to-HTML ratio (0.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (0.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶redirect-to-codepen/reconciliation/no-index-used-as-key 200 79 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Title tag
    Consider adding a title tag to help search engines understand this page's content and improve its appearance in search results.
  2. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  3. Recommended MISSING: Canonical tag
    A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs.
  4. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  5. Recommended THIN CONTENT: Only 79 words
    This page has limited text content (79 words). Expanding the content could improve its relevance for search queries and provide more value to visitors.
  6. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  7. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  8. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  9. Informational CONTENT: Very low text-to-HTML ratio (0.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (0.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶redirect-to-codepen/uncontrolled-components/input-type-file 200 79 9 At Risk Indexable
  1. Pre-Launch Priority MISSING: Title tag
    Consider adding a title tag to help search engines understand this page's content and improve its appearance in search results.
  2. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  3. Recommended MISSING: Canonical tag
    A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs.
  4. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  5. Recommended THIN CONTENT: Only 79 words
    This page has limited text content (79 words). Expanding the content could improve its relevance for search queries and provide more value to visitors.
  6. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  7. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  8. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  9. Informational CONTENT: Very low text-to-HTML ratio (0.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (0.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶versions React - Versions 200 172 9 At Risk No: canonical elsewhere
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended THIN CONTENT: Only 172 words
    This page has limited text content (172 words). Expanding the content could improve its relevance for search queries and provide more value to visitors.
  5. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  6. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  7. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  8. Informational META: Title too short (16 chars, recommended min 30)
    The title tag is only 16 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  9. Informational CONTENT: Very low text-to-HTML ratio (1.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (1.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶blog/2018/09/10/introducing-the-react-profiler.html Introducing the React Profiler – React Blog 200 1398 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 21 images missing alt text
    Some images are missing alt text (1 of 21 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 20 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (20 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 iframes without title attribute
    Some iframes lack title attributes (1 iframes without title attribute). Adding titles improves accessibility by helping screen readers describe embedded content.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (134 KB, recommended <100KB)
    The page weighs 134 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/accessibility.html Accessibility – React 200 3404 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 6 images missing alt text
    Some images are missing alt text (1 of 6 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 5 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (5 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (21 chars, recommended min 30)
    The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (9.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (190 KB, recommended <100KB)
    The page weighs 190 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/components-and-props.html Components and Props – React 200 1703 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (148 KB, recommended <100KB)
    The page weighs 148 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/context.html Context – React 200 3262 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (15 chars, recommended min 30)
    The title tag is only 15 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (9.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (193 KB, recommended <100KB)
    The page weighs 193 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/design-principles.html Design Principles – React 200 3212 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational PERFORMANCE: Large page (136 KB, recommended <100KB)
    The page weighs 136 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/dom-elements.html DOM Elements – React 200 1740 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (20 chars, recommended min 30)
    The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (8.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (133 KB, recommended <100KB)
    The page weighs 133 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/error-boundaries.html Error Boundaries – React 200 1554 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 4 images missing alt text
    Some images are missing alt text (1 of 4 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 3 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (3 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (24 chars, recommended min 30)
    The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (133 KB, recommended <100KB)
    The page weighs 133 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/events.html SyntheticEvent – React 200 1541 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (142 KB, recommended <100KB)
    The page weighs 142 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/faq-build.html Babel, JSX, and Build Steps – React 200 370 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational CONTENT: Very low text-to-HTML ratio (2.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (109 KB, recommended <100KB)
    The page weighs 109 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/faq-internals.html Virtual DOM and Internals – React 200 530 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (108 KB, recommended <100KB)
    The page weighs 108 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/forms.html Forms – React 200 2150 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (13 chars, recommended min 30)
    The title tag is only 13 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (164 KB, recommended <100KB)
    The page weighs 164 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/forwarding-refs.html Forwarding Refs – React 200 1620 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (135 KB, recommended <100KB)
    The page weighs 135 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/fragments.html Fragments – React 200 837 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (17 chars, recommended min 30)
    The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (126 KB, recommended <100KB)
    The page weighs 126 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/glossary.html Glossary of React Terms – React 200 1723 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Recommended LINKS: 1 mixed-content links (HTTP on HTTPS page)
    Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (132 KB, recommended <100KB)
    The page weighs 132 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/handling-events.html Handling Events – React 200 1215 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (5.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (132 KB, recommended <100KB)
    The page weighs 132 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/hello-world.html Hello World – React 200 707 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (19 chars, recommended min 30)
    The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (114 KB, recommended <100KB)
    The page weighs 114 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/hooks-faq.html Hooks FAQ – React 200 7730 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Recommended LINKS: 2 mixed-content links (HTTP on HTTPS page)
    Some links on this HTTPS page point to HTTP URLs (2 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings.
  7. Informational META: Title too short (17 chars, recommended min 30)
    The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational PERFORMANCE: Large page (273 KB, recommended <100KB)
    The page weighs 273 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/hooks-state.html Using the State Hook – React 200 2331 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (152 KB, recommended <100KB)
    The page weighs 152 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/implementation-notes.html Implementation Notes – React 200 5978 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 3 images missing alt text
    Some images are missing alt text (1 of 3 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 2 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (2 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational PERFORMANCE: Large page (228 KB, recommended <100KB)
    The page weighs 228 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/jsx-in-depth.html JSX In Depth – React 200 2818 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (20 chars, recommended min 30)
    The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (8.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (178 KB, recommended <100KB)
    The page weighs 178 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/legacy-context.html Legacy Context – React 200 1428 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (5.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (141 KB, recommended <100KB)
    The page weighs 141 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/legacy-event-pooling.html Event Pooling – React 200 457 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (21 chars, recommended min 30)
    The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (2.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (107 KB, recommended <100KB)
    The page weighs 107 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/lifting-state-up.html Lifting State Up – React 200 2706 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 3 images missing alt text
    Some images are missing alt text (1 of 3 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (24 chars, recommended min 30)
    The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (9.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (164 KB, recommended <100KB)
    The page weighs 164 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/portals.html Portals – React 200 1186 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (15 chars, recommended min 30)
    The title tag is only 15 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (5.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (127 KB, recommended <100KB)
    The page weighs 127 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/profiler.html Profiler API – React 200 1052 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (20 chars, recommended min 30)
    The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (4.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (124 KB, recommended <100KB)
    The page weighs 124 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/react-dom-client.html ReactDOMClient – React 200 832 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (4.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (116 KB, recommended <100KB)
    The page weighs 116 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/react-dom-server.html ReactDOMServer – React 200 1527 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (133 KB, recommended <100KB)
    The page weighs 133 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/react-dom.html ReactDOM – React 200 1648 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (16 chars, recommended min 30)
    The title tag is only 16 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (128 KB, recommended <100KB)
    The page weighs 128 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/react-without-es6.html React Without ES6 – React 200 1364 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (5.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (136 KB, recommended <100KB)
    The page weighs 136 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/react-without-jsx.html React Without JSX – React 200 636 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (113 KB, recommended <100KB)
    The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/reconciliation.html Reconciliation – React 200 1760 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (131 KB, recommended <100KB)
    The page weighs 131 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/render-props.html Render Props – React 200 2347 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (20 chars, recommended min 30)
    The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (160 KB, recommended <100KB)
    The page weighs 160 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/rendering-elements.html Rendering Elements – React 200 875 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 3 images missing alt text
    Some images are missing alt text (1 of 3 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 2 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (2 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (26 chars, recommended min 30)
    The title tag is only 26 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (4.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (120 KB, recommended <100KB)
    The page weighs 120 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/state-and-lifecycle.html State and Lifecycle – React 200 2622 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (27 chars, recommended min 30)
    The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (172 KB, recommended <100KB)
    The page weighs 172 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/static-type-checking.html Static Type Checking – React 200 2042 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (8.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (139 KB, recommended <100KB)
    The page weighs 139 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/test-renderer.html Test Renderer – React 200 1502 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (21 chars, recommended min 30)
    The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (150 KB, recommended <100KB)
    The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/test-utils.html Test Utilities – React 200 1528 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (148 KB, recommended <100KB)
    The page weighs 148 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/typechecking-with-proptypes.html Typechecking With PropTypes – React 200 1551 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (137 KB, recommended <100KB)
    The page weighs 137 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/uncontrolled-components.html Uncontrolled Components – React 200 1017 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational CONTENT: Very low text-to-HTML ratio (4.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (127 KB, recommended <100KB)
    The page weighs 127 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/web-components.html Web Components – React 200 718 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (116 KB, recommended <100KB)
    The page weighs 116 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶languages React - Languages 200 255 8 At Risk No: canonical elsewhere
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended THIN CONTENT: Only 255 words
    This page has limited text content (255 words). Expanding the content could improve its relevance for search queries and provide more value to visitors.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational META: Title too short (17 chars, recommended min 30)
    The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (2.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶warnings/unknown-prop.html Unknown Prop Warning – React 200 810 8 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (4.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (113 KB, recommended <100KB)
    The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶/ React – A JavaScript library for building user... 200 426 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶acknowledgements.html React - Acknowledgements 200 2302 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (24 chars, recommended min 30)
    The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational PERFORMANCE: Large page (117 KB, recommended <100KB)
    The page weighs 117 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2015/12/18/react-components-elements-and-instances.html React Components, Elements, and Instances – React Blog 200 2586 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (9.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (143 KB, recommended <100KB)
    The page weighs 143 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2016/02/19/new-versioning-scheme.html New Versioning Scheme – React Blog 200 791 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 9 images missing alt text
    Some images are missing alt text (1 of 9 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 8 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (8 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (112 KB, recommended <100KB)
    The page weighs 112 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2017/07/26/error-handling-in-react-16.html Error Handling in React 16 – React Blog 200 1140 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 4 images missing alt text
    Some images are missing alt text (1 of 4 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 3 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (3 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (113 KB, recommended <100KB)
    The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2017/09/08/dom-attributes-in-react-16.html DOM Attributes in React 16 – React Blog 200 1328 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (6.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (116 KB, recommended <100KB)
    The page weighs 116 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2017/11/28/react-v16.2.0-fragment-support.html React v16.2.0: Improved Support for Fragments... 200 1776 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (7.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (138 KB, recommended <100KB)
    The page weighs 138 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/composition-vs-inheritance.html Composition vs Inheritance – React 200 1164 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (138 KB, recommended <100KB)
    The page weighs 138 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/hooks-custom.html Building Your Own Hooks – React 200 2112 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (7.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (149 KB, recommended <100KB)
    The page weighs 149 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/hooks-effect.html Using the Effect Hook – React 200 4198 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (29 chars, recommended min 30)
    The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational PERFORMANCE: Large page (191 KB, recommended <100KB)
    The page weighs 191 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/hooks-reference.html Hooks API Reference – React 200 5684 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (27 chars, recommended min 30)
    The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational PERFORMANCE: Large page (229 KB, recommended <100KB)
    The page weighs 229 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/integrating-with-other-libraries.html Integrating with Other Libraries – React 200 3401 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (9.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (184 KB, recommended <100KB)
    The page weighs 184 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/javascript-environment-requirements.html JavaScript Environment Requirements – React 200 374 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (2.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (107 KB, recommended <100KB)
    The page weighs 107 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/optimizing-performance.html Optimizing Performance – React 200 2775 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 5 images missing alt text
    Some images are missing alt text (1 of 5 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 4 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (4 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational CONTENT: Very low text-to-HTML ratio (9.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (162 KB, recommended <100KB)
    The page weighs 162 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/react-api.html React Top-Level API – React 200 2824 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (27 chars, recommended min 30)
    The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational PERFORMANCE: Large page (168 KB, recommended <100KB)
    The page weighs 168 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/react-component.html React.Component – React 200 4808 7 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational PERFORMANCE: Large page (193 KB, recommended <100KB)
    The page weighs 193 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2016/07/13/mixins-considered-harmful.html Mixins Considered Harmful – React Blog 200 4881 6 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational PERFORMANCE: Large page (191 KB, recommended <100KB)
    The page weighs 191 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2018/03/27/update-on-async-rendering.html Update on Async Rendering – React Blog 200 4329 6 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational PERFORMANCE: Large page (193 KB, recommended <100KB)
    The page weighs 193 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2018/06/07/you-probably-dont-need-derived-state.html You Probably Don't Need Derived State – React Blog 200 3379 6 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational PERFORMANCE: Large page (153 KB, recommended <100KB)
    The page weighs 153 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2018/11/27/react-16-roadmap.html React 16.x Roadmap – React Blog 200 2958 6 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational PERFORMANCE: Large page (130 KB, recommended <100KB)
    The page weighs 130 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2022/03/08/react-18-upgrade-guide.html How to Upgrade to React 18 – React Blog 200 2909 6 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational PERFORMANCE: Large page (140 KB, recommended <100KB)
    The page weighs 140 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶docs/higher-order-components.html Higher-Order Components – React 200 3012 6 At Risk Indexable
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 of 2 images missing alt text
    Some images are missing alt text (1 of 2 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended ACCESSIBILITY: 1 form inputs missing labels
    Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology.
  6. Informational PERFORMANCE: Large page (161 KB, recommended <100KB)
    The page weighs 161 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶community/support.html (no title) 308 0 1 Needs Attention --
  1. Recommended REDIRECT: 308 redirect to an off-site URL (https://react.dev/community) -- not crawled
    Note: REDIRECT: 308 redirect to an off-site URL (https://react.dev/community) -- not crawled
▶docs/add-react-to-a-website.html (no title) 308 0 1 Needs Attention --
  1. Recommended REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn/add-react-to-an-existing-project) -- not crawled
    Note: REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn/add-react-to-an-existing-project) -- not crawled
▶docs/create-a-new-react-app.html (no title) 308 0 1 Needs Attention --
  1. Recommended REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn/start-a-new-react-project) -- not crawled
    Note: REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn/start-a-new-react-project) -- not crawled
▶docs/getting-started.html (no title) 308 0 1 Needs Attention --
  1. Recommended REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn) -- not crawled
    Note: REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn) -- not crawled
▶docs/release-channels.html (no title) 308 0 1 Needs Attention --
  1. Recommended REDIRECT: 308 redirect to an off-site URL (https://react.dev/community/versioning-policy) -- not crawled
    Note: REDIRECT: 308 redirect to an off-site URL (https://react.dev/community/versioning-policy) -- not crawled
▶docs/thinking-in-react.html (no title) 308 0 1 Needs Attention --
  1. Recommended REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn/thinking-in-react) -- not crawled
    Note: REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn/thinking-in-react) -- not crawled
▶tutorial/tutorial.html (no title) 308 0 1 Needs Attention --
  1. Recommended REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn/tutorial-tic-tac-toe) -- not crawled
    Note: REDIRECT: 308 redirect to an off-site URL (https://react.dev/learn/tutorial-tic-tac-toe) -- not crawled
Can search engines list these pages?

Of 100 URLs Webtrace requested or found, 88 send signals that allow indexing; 7 redirect; 2 name another URL as canonical; 3 answer with an error.

88 of 100
Indexable (signals allow it)
12
Not indexable
0
Unknown
0
Pages with conflicting signals
8
Redirects met
VerdictURLsShare
Signals allow indexing8888.0%
Canonical points elsewhere22.0%
Redirects77.0%
Error answer (4xx/5xx)33.0%

A raw HTML verdict: Webtrace reads the robots directives, canonicals, redirects and status codes in each answer. These are the signals that allow or prevent indexing, not a search engine's actual index status, and tags inserted by JavaScript are not seen. Googlebot's robots.txt rules are replayed from the copy stored with the crawl.

Conflicting signals

No page sends signals that contradict each other.

URLs that are not indexable or unknown (12)
URLVerdictWhyPoints toFound via
/docs/getting-started.html Redirects 308 redirect to https://react.dev/learn https://react.dev/learn spider
/tutorial/tutorial.html Redirects 308 redirect to https://react.dev/learn/tutorial-tic-tac-toe https://react.dev/learn/tutorial-tic-tac-toe spider
/blog Error answer (4xx/5xx) HTTP 404 -- spider
/community/support.html Redirects 308 redirect to https://react.dev/community https://react.dev/community spider
/versions Canonical points elsewhere canonical points to https://legacy.reactjs.org/versions/ https://legacy.reactjs.org/versions/ spider
/languages Canonical points elsewhere canonical points to https://legacy.reactjs.org/languages/ https://legacy.reactjs.org/languages/ spider
/docs/add-react-to-a-website.html Redirects 308 redirect to https://react.dev/learn/add-react-to-an-existing-project https://react.dev/learn/add-react-to-an-existing-project spider
/docs/create-a-new-react-app.html Redirects 308 redirect to https://react.dev/learn/start-a-new-react-project https://react.dev/learn/start-a-new-react-project spider
/docs/release-channels.html Redirects 308 redirect to https://react.dev/community/versioning-policy https://react.dev/community/versioning-policy spider
/docs/thinking-in-react.html Redirects 308 redirect to https://react.dev/learn/thinking-in-react https://react.dev/learn/thinking-in-react spider
/docs/more-about-refs.html Error answer (4xx/5xx) HTTP 404 -- spider
/docs/webcomponents.html Error answer (4xx/5xx) HTTP 404 -- spider
Redirects the crawl met (8)

Each step is shown as requested. Same-site addresses are shortened to the path. "address form" means the same page under another form of its address (http and https, www, a trailing slash).

Start URLChainHopsFlagsLinked fromFound via
/community/support.html
/community/support.html--308--> https://react.dev/community
1 off-site, not followed 93 spider
/docs/getting-started.html
/docs/getting-started.html--308--> https://react.dev/learn
1 off-site, not followed 93 spider
/tutorial/tutorial.html
/tutorial/tutorial.html--308--> https://react.dev/learn/tutorial-tic-tac-toe
1 off-site, not followed 93 spider
/docs/add-react-to-a-website.html
/docs/add-react-to-a-website.html--308--> https://react.dev/learn/add-react-to-an-existing-project
1 off-site, not followed 71 spider
/docs/create-a-new-react-app.html
/docs/create-a-new-react-app.html--308--> https://react.dev/learn/start-a-new-react-project
1 off-site, not followed 71 spider
/docs/release-channels.html
/docs/release-channels.html--308--> https://react.dev/community/versioning-policy
1 off-site, not followed 71 spider
/docs/thinking-in-react.html
/docs/thinking-in-react.html--308--> https://react.dev/learn/thinking-in-react
1 off-site, not followed 71 spider
/blog/
/blog/--308--> /blog [404]
1 address form 93 spider
robots.txt

http://legacy.reactjs.org/robots.txt: parsed -- its rules apply HTTP 200, 33 bytes

Show the file (2 lines) 
User-agent: *
Disallow: /version/

https://legacy.reactjs.org/robots.txt: parsed -- its rules apply HTTP 200, 33 bytes

Show the file (2 lines) 
User-agent: *
Disallow: /version/
Sections: Site-Wide Achievements Site-Wide Findings Pre-Launch Priority (96) Recommended (413) Informational (223) Implemented Well
Site-Wide Site-Wide Achievements (4) ▲ Sections

Cross-page analysis confirms these site-wide SEO strengths.

site-wide 100% HTTPS internal links -- 100%
All internal links use HTTPS, ensuring a consistent secure experience.
site-wide No orphan pages -- All linked
Every page has at least one inbound internal link.
site-wide Fast average response time -- 81ms
The site's average server response time is excellent.
site-wide Strong average content depth -- 1694 words avg
The site maintains substantial content across pages.
Site-Wide Site-Wide Findings (4) ▲ Sections

Cross-page analysis identified these site-wide patterns worth reviewing.

Finding Recommendation
Recommended SITE: 3 pages share duplicate title "React - Page Not Found"
▶ 3 affected pages
Site-wide observation: 3 pages share duplicate title "React - Page Not Found".
Recommended SITE: 3 pages share duplicate H1 "Page Not Found"
▶ 3 affected pages
Site-wide observation: 3 pages share duplicate H1 "Page Not Found".
Recommended SITE: 3 pages share duplicate H1 "Redirecting to Codepen..."
▶ 3 affected pages
Site-wide observation: 3 pages share duplicate H1 "Redirecting to Codepen...".
Recommended SITE: 2 page groups with near-duplicate content
▶ 6 affected pages
Site-wide observation: 2 page groups with near-duplicate content.
Pre-Launch Priority Pre-Launch Priority (96 findings across 93 pages) ▲ Sections
redirect-to-codepen/reconciliation/index-used-as-key (2 findings)
▶
Finding Recommendation
MISSING: Title tag Consider adding a title tag to help search engines understand this page's content and improve its appearance in search results.
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
redirect-to-codepen/reconciliation/no-index-used-as-key (2 findings)
▶
Finding Recommendation
MISSING: Title tag Consider adding a title tag to help search engines understand this page's content and improve its appearance in search results.
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
redirect-to-codepen/uncontrolled-components/input-type-file (2 findings)
▶
Finding Recommendation
MISSING: Title tag Consider adding a title tag to help search engines understand this page's content and improve its appearance in search results.
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
/ (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
acknowledgements.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog (1 findings)
▶
Finding Recommendation
MISSING: Page not found -- this URL returns a 404 error This URL returns a 404 error. The page needs to be created or the URL needs to be redirected.
blog/2015/12/18/react-components-elements-and-instances.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2016/02/19/new-versioning-scheme.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2016/07/13/mixins-considered-harmful.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2017/04/07/react-v15.5.0.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2017/07/26/error-handling-in-react-16.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2017/09/08/dom-attributes-in-react-16.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2017/11/28/react-v16.2.0-fragment-support.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2018/03/27/update-on-async-rendering.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2018/06/07/you-probably-dont-need-derived-state.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2018/09/10/introducing-the-react-profiler.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2018/11/27/react-16-roadmap.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2022/03/08/react-18-upgrade-guide.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/accessibility.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/cdn-links.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/code-splitting.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/codebase-overview.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/components-and-props.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/composition-vs-inheritance.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/conditional-rendering.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/context.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/design-principles.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/dom-elements.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/error-boundaries.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/events.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/faq-ajax.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/faq-build.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/faq-functions.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/faq-internals.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/faq-state.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/faq-structure.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/faq-styling.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/faq-versioning.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/forms.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/forwarding-refs.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/fragments.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/glossary.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/handling-events.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/hello-world.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/higher-order-components.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/hooks-custom.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/hooks-effect.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/hooks-faq.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/hooks-intro.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/hooks-overview.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/hooks-reference.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/hooks-rules.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/hooks-state.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/how-to-contribute.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/implementation-notes.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/integrating-with-other-libraries.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/introducing-jsx.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/javascript-environment-requirements.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/jsx-in-depth.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/legacy-context.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/legacy-event-pooling.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/lifting-state-up.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/lists-and-keys.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/more-about-refs.html (1 findings)
▶
Finding Recommendation
MISSING: Page not found -- this URL returns a 404 error This URL returns a 404 error. The page needs to be created or the URL needs to be redirected.
docs/optimizing-performance.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/portals.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/profiler.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/react-api.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/react-component.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/react-dom-client.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/react-dom-server.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/react-dom.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/react-without-es6.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/react-without-jsx.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/reconciliation.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/refs-and-the-dom.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/render-props.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/rendering-elements.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/state-and-lifecycle.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/static-type-checking.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/strict-mode.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/test-renderer.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/test-utils.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/testing-environments.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/testing-recipes.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/testing.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/typechecking-with-proptypes.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/uncontrolled-components.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/web-components.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
docs/webcomponents.html (1 findings)
▶
Finding Recommendation
MISSING: Page not found -- this URL returns a 404 error This URL returns a 404 error. The page needs to be created or the URL needs to be redirected.
languages (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
versions (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
warnings/unknown-prop.html (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
Informational Informational (223 findings across 90 pages) ▲ Sections
blog/2017/04/07/react-v15.5.0.html (3 findings)
▶
Finding Recommendation
META: Title too short (26 chars, recommended min 30) The title tag is only 26 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (126 KB, recommended <100KB) The page weighs 126 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/accessibility.html (3 findings)
▶
Finding Recommendation
META: Title too short (21 chars, recommended min 30) The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (9.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (190 KB, recommended <100KB) The page weighs 190 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/cdn-links.html (3 findings)
▶
Finding Recommendation
META: Title too short (17 chars, recommended min 30) The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (116 KB, recommended <100KB) The page weighs 116 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/code-splitting.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (152 KB, recommended <100KB) The page weighs 152 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/codebase-overview.html (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (131 KB, recommended <100KB) The page weighs 131 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/components-and-props.html (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (148 KB, recommended <100KB) The page weighs 148 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/conditional-rendering.html (3 findings)
▶
Finding Recommendation
META: Title too short (29 chars, recommended min 30) The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (150 KB, recommended <100KB) The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/context.html (3 findings)
▶
Finding Recommendation
META: Title too short (15 chars, recommended min 30) The title tag is only 15 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (9.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (193 KB, recommended <100KB) The page weighs 193 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/dom-elements.html (3 findings)
▶
Finding Recommendation
META: Title too short (20 chars, recommended min 30) The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (133 KB, recommended <100KB) The page weighs 133 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/error-boundaries.html (3 findings)
▶
Finding Recommendation
META: Title too short (24 chars, recommended min 30) The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (133 KB, recommended <100KB) The page weighs 133 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/events.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (142 KB, recommended <100KB) The page weighs 142 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/faq-ajax.html (3 findings)
▶
Finding Recommendation
META: Title too short (21 chars, recommended min 30) The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (125 KB, recommended <100KB) The page weighs 125 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/faq-state.html (3 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (120 KB, recommended <100KB) The page weighs 120 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/faq-structure.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (111 KB, recommended <100KB) The page weighs 111 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/faq-styling.html (3 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (112 KB, recommended <100KB) The page weighs 112 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/faq-versioning.html (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (115 KB, recommended <100KB) The page weighs 115 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/forms.html (3 findings)
▶
Finding Recommendation
META: Title too short (13 chars, recommended min 30) The title tag is only 13 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (164 KB, recommended <100KB) The page weighs 164 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/forwarding-refs.html (3 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (135 KB, recommended <100KB) The page weighs 135 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/fragments.html (3 findings)
▶
Finding Recommendation
META: Title too short (17 chars, recommended min 30) The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (126 KB, recommended <100KB) The page weighs 126 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/handling-events.html (3 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (132 KB, recommended <100KB) The page weighs 132 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/hello-world.html (3 findings)
▶
Finding Recommendation
META: Title too short (19 chars, recommended min 30) The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (114 KB, recommended <100KB) The page weighs 114 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/hooks-intro.html (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (128 KB, recommended <100KB) The page weighs 128 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/hooks-overview.html (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (150 KB, recommended <100KB) The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/hooks-rules.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (126 KB, recommended <100KB) The page weighs 126 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/hooks-state.html (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (152 KB, recommended <100KB) The page weighs 152 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/how-to-contribute.html (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (136 KB, recommended <100KB) The page weighs 136 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/introducing-jsx.html (3 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (132 KB, recommended <100KB) The page weighs 132 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/jsx-in-depth.html (3 findings)
▶
Finding Recommendation
META: Title too short (20 chars, recommended min 30) The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (178 KB, recommended <100KB) The page weighs 178 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/legacy-context.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (141 KB, recommended <100KB) The page weighs 141 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/legacy-event-pooling.html (3 findings)
▶
Finding Recommendation
META: Title too short (21 chars, recommended min 30) The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (107 KB, recommended <100KB) The page weighs 107 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/lifting-state-up.html (3 findings)
▶
Finding Recommendation
META: Title too short (24 chars, recommended min 30) The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (9.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (164 KB, recommended <100KB) The page weighs 164 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/lists-and-keys.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (157 KB, recommended <100KB) The page weighs 157 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/portals.html (3 findings)
▶
Finding Recommendation
META: Title too short (15 chars, recommended min 30) The title tag is only 15 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (127 KB, recommended <100KB) The page weighs 127 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/profiler.html (3 findings)
▶
Finding Recommendation
META: Title too short (20 chars, recommended min 30) The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (124 KB, recommended <100KB) The page weighs 124 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/react-dom-client.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (116 KB, recommended <100KB) The page weighs 116 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/react-dom-server.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (133 KB, recommended <100KB) The page weighs 133 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/react-dom.html (3 findings)
▶
Finding Recommendation
META: Title too short (16 chars, recommended min 30) The title tag is only 16 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (128 KB, recommended <100KB) The page weighs 128 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/react-without-es6.html (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (136 KB, recommended <100KB) The page weighs 136 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/react-without-jsx.html (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (113 KB, recommended <100KB) The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/reconciliation.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (131 KB, recommended <100KB) The page weighs 131 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/refs-and-the-dom.html (3 findings)
▶
Finding Recommendation
META: Title too short (24 chars, recommended min 30) The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (149 KB, recommended <100KB) The page weighs 149 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/render-props.html (3 findings)
▶
Finding Recommendation
META: Title too short (20 chars, recommended min 30) The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (160 KB, recommended <100KB) The page weighs 160 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/rendering-elements.html (3 findings)
▶
Finding Recommendation
META: Title too short (26 chars, recommended min 30) The title tag is only 26 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (120 KB, recommended <100KB) The page weighs 120 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/state-and-lifecycle.html (3 findings)
▶
Finding Recommendation
META: Title too short (27 chars, recommended min 30) The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (172 KB, recommended <100KB) The page weighs 172 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/static-type-checking.html (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (139 KB, recommended <100KB) The page weighs 139 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/strict-mode.html (3 findings)
▶
Finding Recommendation
META: Title too short (19 chars, recommended min 30) The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (9.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (136 KB, recommended <100KB) The page weighs 136 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/test-renderer.html (3 findings)
▶
Finding Recommendation
META: Title too short (21 chars, recommended min 30) The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (150 KB, recommended <100KB) The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/test-utils.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (148 KB, recommended <100KB) The page weighs 148 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/testing-environments.html (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (119 KB, recommended <100KB) The page weighs 119 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/testing-recipes.html (3 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (212 KB, recommended <100KB) The page weighs 212 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/testing.html (3 findings)
▶
Finding Recommendation
META: Title too short (24 chars, recommended min 30) The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (113 KB, recommended <100KB) The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/web-components.html (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (116 KB, recommended <100KB) The page weighs 116 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
warnings/unknown-prop.html (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (113 KB, recommended <100KB) The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
acknowledgements.html (2 findings)
▶
Finding Recommendation
META: Title too short (24 chars, recommended min 30) The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
PERFORMANCE: Large page (117 KB, recommended <100KB) The page weighs 117 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2015/12/18/react-components-elements-and-instances.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (9.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (143 KB, recommended <100KB) The page weighs 143 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2016/02/19/new-versioning-scheme.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (4.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (112 KB, recommended <100KB) The page weighs 112 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2017/07/26/error-handling-in-react-16.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (113 KB, recommended <100KB) The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2017/09/08/dom-attributes-in-react-16.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (6.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (116 KB, recommended <100KB) The page weighs 116 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2017/11/28/react-v16.2.0-fragment-support.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (7.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (138 KB, recommended <100KB) The page weighs 138 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2018/09/10/introducing-the-react-profiler.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (6.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (134 KB, recommended <100KB) The page weighs 134 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/composition-vs-inheritance.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (4.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (138 KB, recommended <100KB) The page weighs 138 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/design-principles.html (2 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
PERFORMANCE: Large page (136 KB, recommended <100KB) The page weighs 136 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/faq-build.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (2.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (109 KB, recommended <100KB) The page weighs 109 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/faq-functions.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (6.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (165 KB, recommended <100KB) The page weighs 165 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/faq-internals.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (3.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (108 KB, recommended <100KB) The page weighs 108 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/glossary.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (7.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (132 KB, recommended <100KB) The page weighs 132 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/hooks-custom.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (7.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (149 KB, recommended <100KB) The page weighs 149 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/hooks-effect.html (2 findings)
▶
Finding Recommendation
META: Title too short (29 chars, recommended min 30) The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
PERFORMANCE: Large page (191 KB, recommended <100KB) The page weighs 191 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/hooks-faq.html (2 findings)
▶
Finding Recommendation
META: Title too short (17 chars, recommended min 30) The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
PERFORMANCE: Large page (273 KB, recommended <100KB) The page weighs 273 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/hooks-reference.html (2 findings)
▶
Finding Recommendation
META: Title too short (27 chars, recommended min 30) The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
PERFORMANCE: Large page (229 KB, recommended <100KB) The page weighs 229 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/implementation-notes.html (2 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
PERFORMANCE: Large page (228 KB, recommended <100KB) The page weighs 228 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/integrating-with-other-libraries.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (9.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (184 KB, recommended <100KB) The page weighs 184 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/javascript-environment-requirements.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (2.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (107 KB, recommended <100KB) The page weighs 107 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/optimizing-performance.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (9.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (162 KB, recommended <100KB) The page weighs 162 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/react-api.html (2 findings)
▶
Finding Recommendation
META: Title too short (27 chars, recommended min 30) The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
PERFORMANCE: Large page (168 KB, recommended <100KB) The page weighs 168 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/react-component.html (2 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
PERFORMANCE: Large page (193 KB, recommended <100KB) The page weighs 193 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/typechecking-with-proptypes.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (6.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (137 KB, recommended <100KB) The page weighs 137 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/uncontrolled-components.html (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (4.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (127 KB, recommended <100KB) The page weighs 127 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
languages (2 findings)
▶
Finding Recommendation
META: Title too short (17 chars, recommended min 30) The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
versions (2 findings)
▶
Finding Recommendation
META: Title too short (16 chars, recommended min 30) The title tag is only 16 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (1.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (1.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
/ (1 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (3.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
blog/2016/07/13/mixins-considered-harmful.html (1 findings)
▶
Finding Recommendation
PERFORMANCE: Large page (191 KB, recommended <100KB) The page weighs 191 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2018/03/27/update-on-async-rendering.html (1 findings)
▶
Finding Recommendation
PERFORMANCE: Large page (193 KB, recommended <100KB) The page weighs 193 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2018/06/07/you-probably-dont-need-derived-state.html (1 findings)
▶
Finding Recommendation
PERFORMANCE: Large page (153 KB, recommended <100KB) The page weighs 153 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2018/11/27/react-16-roadmap.html (1 findings)
▶
Finding Recommendation
PERFORMANCE: Large page (130 KB, recommended <100KB) The page weighs 130 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2022/03/08/react-18-upgrade-guide.html (1 findings)
▶
Finding Recommendation
PERFORMANCE: Large page (140 KB, recommended <100KB) The page weighs 140 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
docs/higher-order-components.html (1 findings)
▶
Finding Recommendation
PERFORMANCE: Large page (161 KB, recommended <100KB) The page weighs 161 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
redirect-to-codepen/reconciliation/index-used-as-key (1 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (0.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (0.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
redirect-to-codepen/reconciliation/no-index-used-as-key (1 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (0.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (0.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
redirect-to-codepen/uncontrolled-components/input-type-file (1 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (0.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (0.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
Implemented Well SEO Best Practices Implemented (2156 findings across 97 pages) ▲ Sections

These elements have been properly implemented, demonstrating strong SEO foundations. Click any page to expand its findings.

blog/2016/07/13/mixins-considered-harmful.html (26 findings)
▶
meta Title tag present -- 38 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 38 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2016/07/13/mixins-considered-harmful.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Mixins Considered Harmful
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 4881 words
The page has adequate content for search relevance.
content Strong content depth -- 4881 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 13.8%
The page has a good balance of content vs. markup.
content Clean URL structure -- /blog/2016/07/13/mixins-considered-harmful.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 70ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2018/03/27/update-on-async-rendering.html (26 findings)
▶
meta Title tag present -- 38 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 38 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2018/03/27/update-on-async-rendering.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Update on Async Rendering
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 4329 words
The page has adequate content for search relevance.
content Strong content depth -- 4329 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 12.9%
The page has a good balance of content vs. markup.
content Clean URL structure -- /blog/2018/03/27/update-on-async-rendering.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 157ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2018/06/07/you-probably-dont-need-derived-state.html (26 findings)
▶
meta Title tag present -- 50 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 50 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- You Probably Don't Need Derived State
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 3379 words
The page has adequate content for search relevance.
content Strong content depth -- 3379 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 12.2%
The page has a good balance of content vs. markup.
content Clean URL structure -- /blog/2018/06/07/you-probably-dont-need-derived-state.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 64ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2018/11/27/react-16-roadmap.html (26 findings)
▶
meta Title tag present -- 31 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 31 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2018/11/27/react-16-roadmap.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React 16.x Roadmap
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2958 words
The page has adequate content for search relevance.
content Strong content depth -- 2958 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 13.1%
The page has a good balance of content vs. markup.
content Clean URL structure -- /blog/2018/11/27/react-16-roadmap.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 70ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2022/03/08/react-18-upgrade-guide.html (26 findings)
▶
meta Title tag present -- 39 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 39 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- How to Upgrade to React 18
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2909 words
The page has adequate content for search relevance.
content Strong content depth -- 2909 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 12.0%
The page has a good balance of content vs. markup.
content Clean URL structure -- /blog/2022/03/08/react-18-upgrade-guide.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 70ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/higher-order-components.html (26 findings)
▶
meta Title tag present -- 31 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 31 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/higher-order-components.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Higher-Order Components
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 3012 words
The page has adequate content for search relevance.
content Strong content depth -- 3012 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 11.0%
The page has a good balance of content vs. markup.
content Clean URL structure -- /docs/higher-order-components.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2015/12/18/react-components-elements-and-instances.html (25 findings)
▶
meta Title tag present -- 54 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 54 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Components, Elements, and Instances
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2586 words
The page has adequate content for search relevance.
content Strong content depth -- 2586 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2015/12/18/react-components-elements-and-instances.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 65ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2016/02/19/new-versioning-scheme.html (25 findings)
▶
meta Title tag present -- 34 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 34 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2016/02/19/new-versioning-scheme.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- New Versioning Scheme
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 791 words
The page has adequate content for search relevance.
content Strong content depth -- 791 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2016/02/19/new-versioning-scheme.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 79ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2017/07/26/error-handling-in-react-16.html (25 findings)
▶
meta Title tag present -- 39 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 39 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2017/07/26/error-handling-in-react-16.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Error Handling in React 16
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1140 words
The page has adequate content for search relevance.
content Strong content depth -- 1140 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2017/07/26/error-handling-in-react-16.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 93ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2017/09/08/dom-attributes-in-react-16.html (25 findings)
▶
meta Title tag present -- 39 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 39 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- DOM Attributes in React 16
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1328 words
The page has adequate content for search relevance.
content Strong content depth -- 1328 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2017/09/08/dom-attributes-in-react-16.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 63ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2017/11/28/react-v16.2.0-fragment-support.html (25 findings)
▶
meta Title tag present -- 58 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 58 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2017/11/28/react-v16.2.0-fragment-support.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React v16.2.0: Improved Support for Fragments
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1776 words
The page has adequate content for search relevance.
content Strong content depth -- 1776 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2017/11/28/react-v16.2.0-fragment-support.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 72ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2018/09/10/introducing-the-react-profiler.html (25 findings)
▶
meta Title tag present -- 43 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 43 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2018/09/10/introducing-the-react-profiler.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Introducing the React Profiler
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1398 words
The page has adequate content for search relevance.
content Strong content depth -- 1398 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2018/09/10/introducing-the-react-profiler.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 67ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/composition-vs-inheritance.html (25 findings)
▶
meta Title tag present -- 34 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 34 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/composition-vs-inheritance.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Composition vs Inheritance
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1164 words
The page has adequate content for search relevance.
content Strong content depth -- 1164 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/composition-vs-inheritance.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 69ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/hooks-custom.html (25 findings)
▶
meta Title tag present -- 31 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 31 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/hooks-custom.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Building Your Own Hooks
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2112 words
The page has adequate content for search relevance.
content Strong content depth -- 2112 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/hooks-custom.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 71ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/hooks-effect.html (25 findings)
▶
meta Title tag present -- 29 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/hooks-effect.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Using the Effect Hook
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 4198 words
The page has adequate content for search relevance.
content Strong content depth -- 4198 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 11.9%
The page has a good balance of content vs. markup.
content Clean URL structure -- /docs/hooks-effect.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 69ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/hooks-reference.html (25 findings)
▶
meta Title tag present -- 27 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/hooks-reference.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Hooks API Reference
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 5684 words
The page has adequate content for search relevance.
content Strong content depth -- 5684 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 14.0%
The page has a good balance of content vs. markup.
content Clean URL structure -- /docs/hooks-reference.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 66ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/integrating-with-other-libraries.html (25 findings)
▶
meta Title tag present -- 40 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 40 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/integrating-with-other-libraries.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Integrating with Other Libraries
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 3401 words
The page has adequate content for search relevance.
content Strong content depth -- 3401 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/integrating-with-other-libraries.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/optimizing-performance.html (25 findings)
▶
meta Title tag present -- 30 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 30 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/optimizing-performance.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Optimizing Performance
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2775 words
The page has adequate content for search relevance.
content Strong content depth -- 2775 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/optimizing-performance.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 66ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/react-api.html (25 findings)
▶
meta Title tag present -- 27 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/react-api.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Top-Level API
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2824 words
The page has adequate content for search relevance.
content Strong content depth -- 2824 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 10.1%
The page has a good balance of content vs. markup.
content Clean URL structure -- /docs/react-api.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/react-component.html (25 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/react-component.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React.Component
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 4808 words
The page has adequate content for search relevance.
content Strong content depth -- 4808 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 15.1%
The page has a good balance of content vs. markup.
content Clean URL structure -- /docs/react-component.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 76ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
/ (24 findings)
▶
meta Title tag present -- 57 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 57 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 426 words
The page has adequate content for search relevance.
content Clean URL structure -- /
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 90ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 83 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
acknowledgements.html (24 findings)
▶
meta Title tag present -- 24 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/acknowledgements.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Acknowledgements
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2302 words
The page has adequate content for search relevance.
content Strong content depth -- 2302 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 13.2%
The page has a good balance of content vs. markup.
content Clean URL structure -- /acknowledgements.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 74ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/accessibility.html (24 findings)
▶
meta Title tag present -- 21 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/accessibility.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Accessibility
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 3404 words
The page has adequate content for search relevance.
content Strong content depth -- 3404 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/accessibility.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 72ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/components-and-props.html (24 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/components-and-props.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Components and Props
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1703 words
The page has adequate content for search relevance.
content Strong content depth -- 1703 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/components-and-props.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 119ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/context.html (24 findings)
▶
meta Title tag present -- 15 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/context.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Context
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 3262 words
The page has adequate content for search relevance.
content Strong content depth -- 3262 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/context.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 64ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/design-principles.html (24 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/design-principles.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Design Principles
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3212 words
The page has adequate content for search relevance.
content Strong content depth -- 3212 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 13.9%
The page has a good balance of content vs. markup.
content Clean URL structure -- /docs/design-principles.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 74ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/dom-elements.html (24 findings)
▶
meta Title tag present -- 20 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/dom-elements.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- DOM Elements
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1740 words
The page has adequate content for search relevance.
content Strong content depth -- 1740 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/dom-elements.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 246ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/error-boundaries.html (24 findings)
▶
meta Title tag present -- 24 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/error-boundaries.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Error Boundaries
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1554 words
The page has adequate content for search relevance.
content Strong content depth -- 1554 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/error-boundaries.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/events.html (24 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/events.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- SyntheticEvent
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1541 words
The page has adequate content for search relevance.
content Strong content depth -- 1541 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/events.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 116ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/forms.html (24 findings)
▶
meta Title tag present -- 13 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/forms.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Forms
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2150 words
The page has adequate content for search relevance.
content Strong content depth -- 2150 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/forms.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 73ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/forwarding-refs.html (24 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/forwarding-refs.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Forwarding Refs
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1620 words
The page has adequate content for search relevance.
content Strong content depth -- 1620 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/forwarding-refs.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 76ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/fragments.html (24 findings)
▶
meta Title tag present -- 17 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/fragments.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Fragments
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 837 words
The page has adequate content for search relevance.
content Strong content depth -- 837 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/fragments.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 76ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/glossary.html (24 findings)
▶
meta Title tag present -- 31 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 31 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/glossary.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Glossary of React Terms
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1723 words
The page has adequate content for search relevance.
content Strong content depth -- 1723 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/glossary.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 200ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/handling-events.html (24 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/handling-events.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Handling Events
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1215 words
The page has adequate content for search relevance.
content Strong content depth -- 1215 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/handling-events.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 72ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/hello-world.html (24 findings)
▶
meta Title tag present -- 19 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/hello-world.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Hello World
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 707 words
The page has adequate content for search relevance.
content Strong content depth -- 707 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/hello-world.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 89ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/hooks-faq.html (24 findings)
▶
meta Title tag present -- 17 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/hooks-faq.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Hooks FAQ
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 7730 words
The page has adequate content for search relevance.
content Strong content depth -- 7730 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 14.9%
The page has a good balance of content vs. markup.
content Clean URL structure -- /docs/hooks-faq.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 72ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/hooks-intro.html (24 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/hooks-intro.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Introducing Hooks
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1806 words
The page has adequate content for search relevance.
content Strong content depth -- 1806 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/hooks-intro.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 77ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/hooks-state.html (24 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/hooks-state.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Using the State Hook
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2331 words
The page has adequate content for search relevance.
content Strong content depth -- 2331 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/hooks-state.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 76ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/implementation-notes.html (24 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/implementation-notes.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Implementation Notes
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 5978 words
The page has adequate content for search relevance.
content Strong content depth -- 5978 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 14.8%
The page has a good balance of content vs. markup.
content Clean URL structure -- /docs/implementation-notes.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 69ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/jsx-in-depth.html (24 findings)
▶
meta Title tag present -- 20 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/jsx-in-depth.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- JSX In Depth
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2818 words
The page has adequate content for search relevance.
content Strong content depth -- 2818 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/jsx-in-depth.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 67ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/legacy-context.html (24 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/legacy-context.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Legacy Context
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1428 words
The page has adequate content for search relevance.
content Strong content depth -- 1428 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/legacy-context.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 72ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/lifting-state-up.html (24 findings)
▶
meta Title tag present -- 24 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/lifting-state-up.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Lifting State Up
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2706 words
The page has adequate content for search relevance.
content Strong content depth -- 2706 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/lifting-state-up.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 81ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/portals.html (24 findings)
▶
meta Title tag present -- 15 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/portals.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Portals
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1186 words
The page has adequate content for search relevance.
content Strong content depth -- 1186 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/portals.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 76ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/profiler.html (24 findings)
▶
meta Title tag present -- 20 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/profiler.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Profiler API
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1052 words
The page has adequate content for search relevance.
content Strong content depth -- 1052 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/profiler.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 75ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/react-dom-client.html (24 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/react-dom-client.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- ReactDOMClient
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 832 words
The page has adequate content for search relevance.
content Strong content depth -- 832 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/react-dom-client.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 64ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/react-dom-server.html (24 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/react-dom-server.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- ReactDOMServer
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1527 words
The page has adequate content for search relevance.
content Strong content depth -- 1527 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/react-dom-server.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 73ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/react-dom.html (24 findings)
▶
meta Title tag present -- 16 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/react-dom.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- ReactDOM
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1648 words
The page has adequate content for search relevance.
content Strong content depth -- 1648 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/react-dom.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 227ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/react-without-es6.html (24 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/react-without-es6.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Without ES6
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1364 words
The page has adequate content for search relevance.
content Strong content depth -- 1364 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/react-without-es6.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 70ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/reconciliation.html (24 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/reconciliation.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Reconciliation
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1760 words
The page has adequate content for search relevance.
content Strong content depth -- 1760 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/reconciliation.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 96ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/render-props.html (24 findings)
▶
meta Title tag present -- 20 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/render-props.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Render Props
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2347 words
The page has adequate content for search relevance.
content Strong content depth -- 2347 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/render-props.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 138ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/rendering-elements.html (24 findings)
▶
meta Title tag present -- 26 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/rendering-elements.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Rendering Elements
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 875 words
The page has adequate content for search relevance.
content Strong content depth -- 875 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/rendering-elements.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 72ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/state-and-lifecycle.html (24 findings)
▶
meta Title tag present -- 27 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/state-and-lifecycle.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- State and Lifecycle
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2622 words
The page has adequate content for search relevance.
content Strong content depth -- 2622 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/state-and-lifecycle.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 69ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/static-type-checking.html (24 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/static-type-checking.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Static Type Checking
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2042 words
The page has adequate content for search relevance.
content Strong content depth -- 2042 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/static-type-checking.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 73ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/test-renderer.html (24 findings)
▶
meta Title tag present -- 21 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/test-renderer.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Test Renderer
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1502 words
The page has adequate content for search relevance.
content Strong content depth -- 1502 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/test-renderer.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 70ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/test-utils.html (24 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/test-utils.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Test Utilities
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1528 words
The page has adequate content for search relevance.
content Strong content depth -- 1528 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/test-utils.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 75ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/typechecking-with-proptypes.html (24 findings)
▶
meta Title tag present -- 35 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 35 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/typechecking-with-proptypes.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Typechecking With PropTypes
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1551 words
The page has adequate content for search relevance.
content Strong content depth -- 1551 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/typechecking-with-proptypes.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 67ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/uncontrolled-components.html (24 findings)
▶
meta Title tag present -- 31 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 31 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/uncontrolled-components.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Uncontrolled Components
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1017 words
The page has adequate content for search relevance.
content Strong content depth -- 1017 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/uncontrolled-components.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/web-components.html (24 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/web-components.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Web Components
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 718 words
The page has adequate content for search relevance.
content Strong content depth -- 718 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/web-components.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 60ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/codebase-overview.html (23 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/codebase-overview.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Codebase Overview
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1457 words
The page has adequate content for search relevance.
content Strong content depth -- 1457 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/codebase-overview.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 66ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/conditional-rendering.html (23 findings)
▶
meta Title tag present -- 29 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/conditional-rendering.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Conditional Rendering
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1592 words
The page has adequate content for search relevance.
content Strong content depth -- 1592 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/conditional-rendering.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 75ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/faq-ajax.html (23 findings)
▶
meta Title tag present -- 21 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/faq-ajax.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- AJAX and APIs
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 887 words
The page has adequate content for search relevance.
content Strong content depth -- 887 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/faq-ajax.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 74ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/faq-build.html (23 findings)
▶
meta Title tag present -- 35 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 35 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/faq-build.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Babel, JSX, and Build Steps
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 370 words
The page has adequate content for search relevance.
content Clean URL structure -- /docs/faq-build.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 75ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/faq-functions.html (23 findings)
▶
meta Title tag present -- 39 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 39 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/faq-functions.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Passing Functions to Components
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2189 words
The page has adequate content for search relevance.
content Strong content depth -- 2189 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/faq-functions.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 71ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/faq-internals.html (23 findings)
▶
meta Title tag present -- 33 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 33 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/faq-internals.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Virtual DOM and Internals
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 530 words
The page has adequate content for search relevance.
content Clean URL structure -- /docs/faq-internals.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 73ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/faq-state.html (23 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/faq-state.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Component State
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 980 words
The page has adequate content for search relevance.
content Strong content depth -- 980 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/faq-state.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 79ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/faq-versioning.html (23 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/faq-versioning.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Versioning Policy
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1247 words
The page has adequate content for search relevance.
content Strong content depth -- 1247 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/faq-versioning.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 79ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/hooks-overview.html (23 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/hooks-overview.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Hooks at a Glance
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2258 words
The page has adequate content for search relevance.
content Strong content depth -- 2258 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/hooks-overview.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 71ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/hooks-rules.html (23 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/hooks-rules.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Rules of Hooks
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1290 words
The page has adequate content for search relevance.
content Strong content depth -- 1290 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/hooks-rules.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/how-to-contribute.html (23 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/how-to-contribute.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- How to Contribute
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2042 words
The page has adequate content for search relevance.
content Strong content depth -- 2042 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/how-to-contribute.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 65ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/introducing-jsx.html (23 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/introducing-jsx.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Introducing JSX
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1279 words
The page has adequate content for search relevance.
content Strong content depth -- 1279 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/introducing-jsx.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 75ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/javascript-environment-requirements.html (23 findings)
▶
meta Title tag present -- 43 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 43 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/javascript-environment-requirements.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- JavaScript Environment Requirements
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 374 words
The page has adequate content for search relevance.
content Clean URL structure -- /docs/javascript-environment-requirements.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 84ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/lists-and-keys.html (23 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/lists-and-keys.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Lists and Keys
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1876 words
The page has adequate content for search relevance.
content Strong content depth -- 1876 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/lists-and-keys.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 66ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/react-without-jsx.html (23 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/react-without-jsx.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Without JSX
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 636 words
The page has adequate content for search relevance.
content Strong content depth -- 636 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/react-without-jsx.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 74ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/refs-and-the-dom.html (23 findings)
▶
meta Title tag present -- 24 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/refs-and-the-dom.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Refs and the DOM
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2171 words
The page has adequate content for search relevance.
content Strong content depth -- 2171 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/refs-and-the-dom.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 69ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/strict-mode.html (23 findings)
▶
meta Title tag present -- 19 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/strict-mode.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Strict Mode
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1996 words
The page has adequate content for search relevance.
content Strong content depth -- 1996 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/strict-mode.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/testing-environments.html (23 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/testing-environments.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Testing Environments
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1125 words
The page has adequate content for search relevance.
content Strong content depth -- 1125 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/testing-environments.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/testing.html (23 findings)
▶
meta Title tag present -- 24 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/testing.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Testing Overview
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 665 words
The page has adequate content for search relevance.
content Strong content depth -- 665 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/testing.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 66ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
languages (23 findings)
▶
meta Title tag present -- 17 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/languages/
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Languages
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Clean URL structure -- /languages/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 69ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 86 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
warnings/unknown-prop.html (23 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/warnings/unknown-prop.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Unknown Prop Warning
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 810 words
The page has adequate content for search relevance.
content Strong content depth -- 810 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /warnings/unknown-prop.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 71ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2017/04/07/react-v15.5.0.html (22 findings)
▶
meta Title tag present -- 26 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React v15.5.0
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1616 words
The page has adequate content for search relevance.
content Strong content depth -- 1616 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2017/04/07/react-v15.5.0.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 80ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/cdn-links.html (22 findings)
▶
meta Title tag present -- 17 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/cdn-links.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- CDN Links
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 484 words
The page has adequate content for search relevance.
content Clean URL structure -- /docs/cdn-links.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 77ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/code-splitting.html (22 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/code-splitting.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Code-Splitting
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1976 words
The page has adequate content for search relevance.
content Strong content depth -- 1976 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/code-splitting.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/faq-structure.html (22 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/faq-structure.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- File Structure
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 730 words
The page has adequate content for search relevance.
content Strong content depth -- 730 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/faq-structure.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 74ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/faq-styling.html (22 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/faq-styling.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Styling and CSS
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 517 words
The page has adequate content for search relevance.
content Clean URL structure -- /docs/faq-styling.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 66ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/legacy-event-pooling.html (22 findings)
▶
meta Title tag present -- 21 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/legacy-event-pooling.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Event Pooling
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 457 words
The page has adequate content for search relevance.
content Clean URL structure -- /docs/legacy-event-pooling.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 66ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
docs/testing-recipes.html (22 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/docs/testing-recipes.html
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Testing Recipes
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3651 words
The page has adequate content for search relevance.
content Strong content depth -- 3651 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /docs/testing-recipes.html
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 72ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
versions (22 findings)
▶
meta Title tag present -- 16 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://legacy.reactjs.org/versions/
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Versions
The page has exactly one H1 heading, clearly defining its main topic.
content Clean URL structure -- /versions/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 63ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 76 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
redirect-to-codepen/reconciliation/index-used-as-key (17 findings)
▶
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Redirecting to Codepen...
The page has exactly one H1 heading, clearly defining its main topic.
content Clean URL structure -- /redirect-to-codepen/reconciliation/index-used-as-key/
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 74ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 65 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
redirect-to-codepen/reconciliation/no-index-used-as-key (17 findings)
▶
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Redirecting to Codepen...
The page has exactly one H1 heading, clearly defining its main topic.
content Clean URL structure -- /redirect-to-codepen/reconciliation/no-index-used-as-key/
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 123ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 65 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
redirect-to-codepen/uncontrolled-components/input-type-file (17 findings)
▶
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Redirecting to Codepen...
The page has exactly one H1 heading, clearly defining its main topic.
content Clean URL structure -- /redirect-to-codepen/uncontrolled-components/input-type-file/
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 65ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 63 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
community/support.html (4 findings)
▶
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
content Clean URL structure -- /community/support.html
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
docs/add-react-to-a-website.html (4 findings)
▶
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
content Clean URL structure -- /docs/add-react-to-a-website.html
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
docs/create-a-new-react-app.html (4 findings)
▶
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
content Clean URL structure -- /docs/create-a-new-react-app.html
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
docs/getting-started.html (4 findings)
▶
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
content Clean URL structure -- /docs/getting-started.html
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
docs/release-channels.html (4 findings)
▶
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
content Clean URL structure -- /docs/release-channels.html
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
docs/thinking-in-react.html (4 findings)
▶
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
content Clean URL structure -- /docs/thinking-in-react.html
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
tutorial/tutorial.html (4 findings)
▶
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
content Clean URL structure -- /tutorial/tutorial.html
The URL is lowercase and concise, following best practices.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.