Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

bejson.com

在线JSON校验格式化工具(Be JSON)

Page Load Speed

21.5 sec in total

First Response

3.7 sec

Resources Loaded

17.6 sec

Page Rendered

210 ms

About Website

Visit bejson.com now to see the best up-to-date Be JSON content for China and also check out these interesting facts you probably never knew about bejson.com

在线,JSON,JSON 校验,格式化,xml转json 工具,在线工具,json视图,可视化,程序,服务器,域名注册,正则表达式,测试,在线json格式化工具,json 格式化,json格式化工具,json字符串格式化,json 在线查看器,json在线,json 在线验证,json tools online,在线文字对比工具

Visit bejson.com

Key Findings

We analyzed Bejson.com page load time and found that the first response time was 3.7 sec and then it took 17.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

bejson.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value1,650 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

bejson.com

3661 ms

www.bejson.com

2714 ms

jquery.min.js

735 ms

bootstrap.min.css

761 ms

bootstrap.min.js

708 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 16% of them (8 requests) were addressed to the original Bejson.com, 22% (11 requests) were made to Cpro.baidustatic.com and 12% (6 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Bejson.qiniudn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.8 kB (51%)

Content Size

532.5 kB

After Optimization

258.7 kB

In fact, the total size of Bejson.com main page is 532.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 440.6 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 16.8 kB

  • Original 25.0 kB
  • After minification 25.0 kB
  • After compression 8.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 16.8 kB or 67% of the original size.

Image Optimization

-53%

Potential reduce by 21.5 kB

  • Original 40.5 kB
  • After minification 19.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, Be JSON needs image optimization as it can save up to 21.5 kB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-52%

Potential reduce by 229.2 kB

  • Original 440.6 kB
  • After minification 438.2 kB
  • After compression 211.5 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 229.2 kB or 52% of the original size.

CSS Optimization

-24%

Potential reduce by 6.4 kB

  • Original 26.5 kB
  • After minification 25.2 kB
  • After compression 20.1 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. Bejson.com needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (46%)

Requests Now

46

After Optimization

25

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

Accessibility Review

bejson.com accessibility score

67

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Names and labels

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.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

bejson.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

bejson.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bejson.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Bejson.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

Open Graph description is not detected on the main page of Be JSON. 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: