Spain · Madrid Completed: Apr 22, 2026 21:12 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 72 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
Several regulatory requirements are not yet met.
Missing metadata means poor previews on social media and search.
Lean and efficient — low environmental impact per visit.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
6 image(s) missing alt attribute
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/2675c44f-642c-43d7-8c3e-e8be8428deeb)<a href="https://beavercheck.com/results/2675c44f-642c-43d7-8c3e-e8be8428deeb"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fjson.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fjson.orgThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
9 barrier(s) likely increasing bounce by ~34%.
Page loads in 2.6s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 114ms over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Layout shifts during page load
+3% bounceContent movement causes mis-clicks on CTAs and form fields
Fix: Add width/height to images; reserve space for late-loading embeds
No viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
42 broken link(s) on the page
+5% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€405 investment → €176/month returns + EUR 20,500,000 risk avoided
€405
4h · 5 findings
€176 /mo
~€2,111 / year
EUR 20,500,000
if kept compliant
€135 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
4.5 developer hours at €90/hr
Based on Germany rates (€90/hr)
Start here for the best return on investment
€1,708,333 / month at risk
~€20,500,001 / year if left unfixed
€20,500,000
+3 more
€0.06 /mo
745.6 MB/mo × 0.074 EUR/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.16 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.61 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.245
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.16 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
2.61 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| www.json.org/Programma-Bold.woff2 | 395 ms |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.json.org/img/string.png | 0.0 ms | 49.3 KiB |
| www.json.org/img/number.png | 0.0 ms | 36.4 KiB |
| www.json.org/Programma-Bold.woff2 | 0.0 ms | 33.7 KiB |
| www.json.org/img/value.png | 0.0 ms | 23.6 KiB |
| www.json.org/img/object.png | 0.0 ms | 19.8 KiB |
| www.json.org/img/whitespace.png | 0.0 ms | 18.3 KiB |
| www.json.org/img/json160.gif | 0.0 ms | 11.9 KiB |
| www.json.org/img/array.png | 0.0 ms | 11.4 KiB |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/string.png | 49.0 KiB | 35.3 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/number.png | 36.1 KiB | 26.0 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/value.png | 23.3 KiB | 16.8 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/object.png | 19.6 KiB | 14.1 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/whitespace.png | 18.1 KiB | 13.0 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/array.png | 11.2 KiB | 8.1 KiB |
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/string.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/number.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/value.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/whitespace.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/object.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/array.png |
More information about the performance of your application. These numbers don't directly affect the Performance score.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| json.org/ | 1.2 s |
| www.json.org/json-en.html | 0.0 ms |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
json
element
value
object
array
string
number
"true"
"false"
"null"
object
… body > div#spec > div#grammar | 0.178 |
body > div#spec > div#text > center body > div#spec > div#text > center | 0.028 |
A string is a sequence of zero or more Unicode characters, wrapped in double qu… body > div#spec > div#text > p | 0.015 |
body > div#spec > div#text > center body > div#spec > div#text > center | 0.013 |
body > div#spec > div#text > center body > div#spec > div#text > center | 0.006 |
Whitespace can be inserted between any pair of tokens. Excepting a few encoding… body > div#spec > div#text > p | 0.004 |
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
العربية body > div > small > a |
Български body > div > small > a |
中文 body > div > small > a |
Český body > div > small > a |
Dansk body > div > small > a |
Nederlands body > div > small > a |
Esperanto body > div > small > a |
Deutsch body > div > small > a |
Ελληνικά body > div > small > a |
עברית body > div > small > a |
Magyar body > div > small > a |
Indonesia body > div > small > a |
Italiano body > div > small > a |
日本 body > div > small > a |
한국어 body > div > small > a |
Norsk body > div > small > a |
Polski body > div > small > a |
Português body > div > small > a |
Română body > div > small > a |
Српско-хрватски body > div > small > a |
Slovenščina body > div > small > a |
Español body > div > small > a |
Svenska body > div > small > a |
Türkçe body > div > small > a |
Українська body > div > small > a |
Tiếng Việt body > div > small > a |
JSON for ASP li > ul > li > a |
JSON ASP utility class li > ul > li > a |
JSON.awk li > ul > li > a |
rhawk li > ul > li > a |
mu_json li > ul > li > a |
JSON_checker li > ul > li > a |
YAJL li > ul > li > a |
LibU li > ul > li > a |
json-c li > ul > li > a |
json-parser li > ul > li > a |
jsonsl li > ul > li > a |
WJElement li > ul > li > a |
M's JSON parser li > ul > li > a |
cJSON li > ul > li > a |
Jansson li > ul > li > a |
jsmn li > ul > li > a |
parson li > ul > li > a |
ujson4c li > ul > li > a |
frozen li > ul > li > a |
microjson li > ul > li > a |
mjson li > ul > li > a |
progbase li > ul > li > a |
lwjson li > ul > li > a |
cisson li > ul > li > a |
nanoJSONc li > ul > li > a |
JSON-BUILD li > ul > li > a |
JSONKit li > ul > li > a |
jsonme-- li > ul > li > a |
ThorsSerializer li > ul > li > a |
JsonBox li > ul > li > a |
jvar li > ul > li > a |
rapidjson li > ul > li > a |
minijson li > ul > li > a |
jsoncons li > ul > li > a |
jsoncpp li > ul > li > a |
univalue li > ul > li > a |
jsovon li > ul > li > a |
ArduinoJson li > ul > li > a |
QJson li > ul > li > a |
CAJUN li > ul > li > a |
libjson li > ul > li > a |
nosjob li > ul > li > a |
qmjson li > ul > li > a |
JSON Support in Qt li > ul > li > a |
JsonWax for Qt li > ul > li > a |
progbase li > ul > li > a |
Qentem-Engine li > ul > li > a |
fastJSON li > ul > li > a |
JSON_checker li > ul > li > a |
Json.NET li > ul > li > a |
JSON for .NET li > ul > li > a |
Manatee Json li > ul > li > a |
FastJsonParser li > ul > li > a |
LightJson li > ul > li > a |
Liersch.Json li > ul > li > a |
Liersch.JsonSerialization li > ul > li > a |
progbase li > ul > li > a |
JSON Essentials li > ul > li > a |
std.json li > ul > li > a |
asdf li > ul > li > a |
Delphi Web Utils li > ul > li > a |
JSON Delphi Library li > ul > li > a |
json-fortran li > ul > li > a |
YAJL-Fort li > ul > li > a |
jsonff li > ul > li > a |
RJson package li > ul > li > a |
json package li > ul > li > a |
JSON-java li > ul > li > a |
esson li > ul > li > a |
JSONUtil li > ul > li > a |
jsonp li > ul > li > a |
Json-lib li > ul > li > a |
Stringtree li > ul > li > a |
SOJO li > ul > li > a |
json-taglib li > ul > li > a |
Flexjson li > ul > li > a |
Argo li > ul > li > a |
jsonij li > ul > li > a |
fastjson li > ul > li > a |
mjson li > ul > li > a |
jjson li > ul > li > a |
json-simple li > ul > li > a |
json-io li > ul > li > a |
google-gson li > ul > li > a |
FOSS Nova JSON li > ul > li > a |
Corn CONVERTER li > ul > li > a |
Apache johnzon li > ul > li > a |
Genson li > ul > li > a |
cookjson li > ul > li > a |
progbase li > ul > li > a |
jackson li > ul > li > a |
MOXy li > ul > li > a |
JSON li > ul > li > a |
json2.js li > ul > li > a |
clarinet li > ul > li > a |
Oboe.js li > ul > li > a |
progbase li > ul > li > a |
JSONlab li > ul > li > a |
20565 li > ul > li > a |
23393 li > ul > li > a |
NSJSONSerialization li > ul > li > a |
json-framework li > ul > li > a |
JSONKit li > ul > li > a |
yajl-objc li > ul > li > a |
TouchJSON li > ul > li > a |
Public.Parser.JSON li > ul > li > a |
Public.Parser.JSON2 li > ul > li > a |
simplejson li > ul > li > a |
pyson li > ul > li > a |
Yajl-Py li > ul > li > a |
ultrajson li > ul > li > a |
metamagic.json li > ul > li > a |
progbase li > ul > li > a |
rjson li > ul > li > a |
jsonlite li > ul > li > a |
Serde JSON li > ul > li > a |
json-rust li > ul > li > a |
yajl-ruby li > ul > li > a |
json-stream li > ul > li > a |
progbase li > ul > li > a |
MZScheme li > ul > li > a |
JSON-struct li > ul > li > a |
Jshon li > ul > li > a |
JSON.sh li > ul > li > a |
jwalk li > ul > li > a |
VB-JSON li > ul > li > a |
PW.JSON li > ul > li > a |
progbase li > ul > li > a |
fwJSON li > ul > li > a |
JSON li > ul > li > a |
vfpjson li > ul > li > a |
Videos about JSON div > ul > li > a |
Videos about the JSON Logo div > ul > li > a |
Heresy & Heretical Open Source: A Heretic's Perspective div > ul > li > a |
Nota Message Format div > ul > li > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
json logo tbody > tr > td > img | www.json.org/img/json160.gif | 160 x 160 | 160 x 160 | 240 x 240 |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
983 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.06 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.037
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
983 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
1.06 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| www.json.org/Programma-Bold.woff2 | 310 ms |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.json.org/img/string.png | 0.0 ms | 49.3 KiB |
| www.json.org/img/number.png | 0.0 ms | 36.4 KiB |
| www.json.org/Programma-Bold.woff2 | 0.0 ms | 33.7 KiB |
| www.json.org/img/value.png | 0.0 ms | 23.6 KiB |
| www.json.org/img/object.png | 0.0 ms | 19.8 KiB |
| www.json.org/img/whitespace.png | 0.0 ms | 18.3 KiB |
| www.json.org/img/json160.gif | 0.0 ms | 11.9 KiB |
| www.json.org/img/array.png | 0.0 ms | 11.4 KiB |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/string.png | 49.0 KiB | 37.5 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/number.png | 36.1 KiB | 27.7 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/value.png | 23.3 KiB | 17.9 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/object.png | 19.6 KiB | 15.0 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/whitespace.png | 18.1 KiB | 13.8 KiB |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/array.png | 11.2 KiB | 8.6 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/string.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/number.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/value.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/whitespace.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/object.png |
div#spec > div#text > center > img div#spec > div#text > center > img | www.json.org/img/array.png |
More information about the performance of your application. These numbers don't directly affect the Performance score.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| json.org/ | 564 ms |
| www.json.org/json-en.html | 0.0 ms |
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
العربية body > div > small > a |
Български body > div > small > a |
中文 body > div > small > a |
Český body > div > small > a |
Dansk body > div > small > a |
Nederlands body > div > small > a |
Esperanto body > div > small > a |
Deutsch body > div > small > a |
Ελληνικά body > div > small > a |
עברית body > div > small > a |
Magyar body > div > small > a |
Indonesia body > div > small > a |
Italiano body > div > small > a |
日本 body > div > small > a |
한국어 body > div > small > a |
Norsk body > div > small > a |
Polski body > div > small > a |
Português body > div > small > a |
Română body > div > small > a |
Српско-хрватски body > div > small > a |
Slovenščina body > div > small > a |
Español body > div > small > a |
Svenska body > div > small > a |
Türkçe body > div > small > a |
Українська body > div > small > a |
Tiếng Việt body > div > small > a |
JSON for ASP li > ul > li > a |
JSON ASP utility class li > ul > li > a |
JSON.awk li > ul > li > a |
rhawk li > ul > li > a |
mu_json li > ul > li > a |
JSON_checker li > ul > li > a |
YAJL li > ul > li > a |
LibU li > ul > li > a |
json-c li > ul > li > a |
json-parser li > ul > li > a |
jsonsl li > ul > li > a |
WJElement li > ul > li > a |
M's JSON parser li > ul > li > a |
cJSON li > ul > li > a |
Jansson li > ul > li > a |
jsmn li > ul > li > a |
parson li > ul > li > a |
ujson4c li > ul > li > a |
frozen li > ul > li > a |
microjson li > ul > li > a |
mjson li > ul > li > a |
progbase li > ul > li > a |
lwjson li > ul > li > a |
cisson li > ul > li > a |
nanoJSONc li > ul > li > a |
JSON-BUILD li > ul > li > a |
JSONKit li > ul > li > a |
jsonme-- li > ul > li > a |
ThorsSerializer li > ul > li > a |
JsonBox li > ul > li > a |
jvar li > ul > li > a |
rapidjson li > ul > li > a |
minijson li > ul > li > a |
jsoncons li > ul > li > a |
jsoncpp li > ul > li > a |
univalue li > ul > li > a |
jsovon li > ul > li > a |
ArduinoJson li > ul > li > a |
QJson li > ul > li > a |
CAJUN li > ul > li > a |
libjson li > ul > li > a |
nosjob li > ul > li > a |
qmjson li > ul > li > a |
JSON Support in Qt li > ul > li > a |
JsonWax for Qt li > ul > li > a |
progbase li > ul > li > a |
Qentem-Engine li > ul > li > a |
fastJSON li > ul > li > a |
JSON_checker li > ul > li > a |
Json.NET li > ul > li > a |
JSON for .NET li > ul > li > a |
Manatee Json li > ul > li > a |
FastJsonParser li > ul > li > a |
LightJson li > ul > li > a |
Liersch.Json li > ul > li > a |
Liersch.JsonSerialization li > ul > li > a |
progbase li > ul > li > a |
JSON Essentials li > ul > li > a |
std.json li > ul > li > a |
asdf li > ul > li > a |
Delphi Web Utils li > ul > li > a |
JSON Delphi Library li > ul > li > a |
json-fortran li > ul > li > a |
YAJL-Fort li > ul > li > a |
jsonff li > ul > li > a |
RJson package li > ul > li > a |
json package li > ul > li > a |
JSON-java li > ul > li > a |
esson li > ul > li > a |
JSONUtil li > ul > li > a |
jsonp li > ul > li > a |
Json-lib li > ul > li > a |
Stringtree li > ul > li > a |
SOJO li > ul > li > a |
json-taglib li > ul > li > a |
Flexjson li > ul > li > a |
Argo li > ul > li > a |
jsonij li > ul > li > a |
fastjson li > ul > li > a |
mjson li > ul > li > a |
jjson li > ul > li > a |
json-simple li > ul > li > a |
json-io li > ul > li > a |
google-gson li > ul > li > a |
FOSS Nova JSON li > ul > li > a |
Corn CONVERTER li > ul > li > a |
Apache johnzon li > ul > li > a |
Genson li > ul > li > a |
cookjson li > ul > li > a |
progbase li > ul > li > a |
jackson li > ul > li > a |
MOXy li > ul > li > a |
JSON li > ul > li > a |
json2.js li > ul > li > a |
clarinet li > ul > li > a |
Oboe.js li > ul > li > a |
progbase li > ul > li > a |
JSONlab li > ul > li > a |
20565 li > ul > li > a |
23393 li > ul > li > a |
NSJSONSerialization li > ul > li > a |
json-framework li > ul > li > a |
JSONKit li > ul > li > a |
yajl-objc li > ul > li > a |
TouchJSON li > ul > li > a |
Public.Parser.JSON li > ul > li > a |
Public.Parser.JSON2 li > ul > li > a |
simplejson li > ul > li > a |
pyson li > ul > li > a |
Yajl-Py li > ul > li > a |
ultrajson li > ul > li > a |
metamagic.json li > ul > li > a |
progbase li > ul > li > a |
rjson li > ul > li > a |
jsonlite li > ul > li > a |
Serde JSON li > ul > li > a |
json-rust li > ul > li > a |
yajl-ruby li > ul > li > a |
json-stream li > ul > li > a |
progbase li > ul > li > a |
MZScheme li > ul > li > a |
JSON-struct li > ul > li > a |
Jshon li > ul > li > a |
JSON.sh li > ul > li > a |
jwalk li > ul > li > a |
VB-JSON li > ul > li > a |
PW.JSON li > ul > li > a |
progbase li > ul > li > a |
fwJSON li > ul > li > a |
JSON li > ul > li > a |
vfpjson li > ul > li > a |
Videos about JSON div > ul > li > a |
Videos about the JSON Logo div > ul > li > a |
Heresy & Heretical Open Source: A Heretic's Perspective div > ul > li > a |
Nota Message Format div > ul > li > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
div#spec > div#text > center > img div#spec > div#text > center > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback