Access jbenglish.org. 米乐(中国)·m6官网首页

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value22.4 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value33.8 s

0/100

10%

jbenglish.org

1094 ms

reset.css

413 ms

animate.min.css

1032 ms

common.css

824 ms

lyz.calendar.css

631 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 80% of them (63 requests) were addressed to the original Jbenglish.org, 8% (6 requests) were made to Asdf7868asdfasdf7.xyz and 5% (4 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (10.3 sec) belongs to the original domain Jbenglish.org.

Content Size

7.0 MB

After Optimization

6.3 MB

In fact, the total size of Jbenglish.org main page is 7.0 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. 60% of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 58.1 kB

Original 69.6 kB
After minification 57.2 kB
After compression 11.4 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.4 kB, which is 18% 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 58.1 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 292.0 kB

Original 6.0 MB
After minification 5.7 MB

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. Jbenglish images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 266.5 kB

Original 822.0 kB
After minification 812.2 kB
After compression 555.4 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 266.5 kB or 32% of the original size.

CSS Optimization

-87%

Potential reduce by 127.8 kB

Original 147.2 kB
After minification 130.7 kB
After compression 19.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. Jbenglish.org needs all CSS files to be minified and compressed as it can save up to 127.8 kB or 87% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

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

<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

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

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

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

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jbenglish.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Jbenglish.org 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

jbenglish.org

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

米乐(中国)·m6官网首页 - 网页版

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

jbenglish.org

reset.css

animate.min.css

common.css

lyz.calendar.css

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

jbenglish.org

reset.css

animate.min.css

common.css

lyz.calendar.css

jquery.js

laydate.js

m8tro-bootstrap-pie.js

swiper.min.css

index.css

data.js

swiper.animate.min.js

swiper.min.js

common.js

index.js

laydate.css

laydate.css

asdf7868asdfasdf7.xyz

hm.js

js-sdk-pro.min.js

5cd92ffae8f7c.png

search_icon.png

code_icon.png

call_icon.png

load_icon.png

search2_icon.png

5d9da3c29013f.png

5dc9260c1d0c0.png

video_btn.png

icon_r.png

5d9da3c943c09.png

5cd917efd2b9b.png

wechat_img.jpg

6603e96a802bb.png

5e1fcb040455b.jpg

5d3650c993bc9.jpg

65d316c260e33.jpg

65d316f9dd3e0.jpg

65d31676e4b13.jpg

5d365b7874ad3.jpg

65d316d0ea77c.jpg

about_icon.png

5d3587bf6932e.jpg