Access json2csharp.com. Convert JSON to C# Classes Online

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.93

3/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

json2csharp.com

211 ms

all.css

88 ms

js

96 ms

lottie-player.js

74 ms

adsbygoogle.js

300 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Json2csharp.com, 57% (50 requests) were made to Freecodegenerators.azureedge.net and 7% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (579 ms) relates to the external source Freecodegenerators.azureedge.net.

Content Size

1.5 MB

After Optimization

1.1 MB

In fact, the total size of Json2csharp.com main page is 1.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 77.6 kB

Original 93.4 kB
After minification 80.6 kB
After compression 15.8 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 12.8 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 77.6 kB or 83% of the original size.

Image Optimization

-26%

Potential reduce by 298.0 kB

Original 1.1 MB
After minification 848.0 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Json2C Sharp needs image optimization as it can save up to 298.0 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 34.7 kB

Original 209.9 kB
After minification 209.9 kB
After compression 175.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 34.7 kB or 17% of the original size.

CSS Optimization

-25%

Potential reduce by 7.3 kB

Original 28.7 kB
After minification 28.7 kB
After compression 21.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Json2csharp.com needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 25% of the original size.

Requests Now

After Optimization

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Json2C Sharp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Json2csharp.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Json2csharp.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

json2csharp.com

Open Graph description is not detected on the main page of Json2C Sharp. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

Report Summary

Performance

Accessibility

Best Practices

SEO

Convert JSON to C# Classes Online - Json2CSharp Toolkit

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

json2csharp.com

all.css

js

lottie-player.js

adsbygoogle.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

json2csharp.com

all.css

js

lottie-player.js

adsbygoogle.js

all.js

jquery-3.6.0.min.js

clipboard.min.js

javascript.js

clike.js

jszip.min.js

filesaver.js

17316acb14.js

lottie-player.js

tenor.gif

menu.png

Logo.png

json-colored.svg

csharp-colored.svg

json-to-csharp-preview.png

xml-colored.svg

xml-to-csharp-preview.png

csharp-object-Initializer.svg

csharp-to-object-preview.png

java-colored.svg

json-to-java-preview.png

xml-to-java-preview.png

python-colored.svg

json-to-python-preview.png

dart-colored.svg

json-to-dart-preview.png

sass-colored.svg

css-colored.svg

scss-to-css-preview.png

less-colored.svg

less-to-css-preview.png

a.svg

ACap.svg

CaseConverterPreview.png

duplicate-lines.svg

no-duplicate-lines.svg

remove-duplicate-lines-banner.png

inner-join.svg