Access byo2.com.

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

68/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value10,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value50.1 s

0/100

10%

index.php

222 ms

common.js

74 ms

tj.js

152 ms

01smt.js

524 ms

smt_data.php

215 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Byo2.com, 36% (31 requests) were made to 2022mry-01.cc and 14% (12 requests) were made to Img.lytuchuang2.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Sz88.oss-cn-shenzhen.aliyuncs.com.

Content Size

1.6 MB

After Optimization

1.5 MB

In fact, the total size of Byo2.com main page is 1.6 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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 5.2 kB

Original 5.6 kB
After minification 5.6 kB
After compression 440 B

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 5.2 kB or 92% of the original size.

Image Optimization

-4%

Potential reduce by 65.7 kB

Original 1.5 MB
After minification 1.5 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. Byo 2 images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 7.3 kB

Original 51.4 kB
After minification 51.4 kB
After compression 44.1 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 7.3 kB or 14% of the original size.

CSS Optimization

-23%

Potential reduce by 11.4 kB

Original 49.2 kB
After minification 49.2 kB
After compression 37.8 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. Byo2.com needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 23% 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 Byo 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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

Document doesn't have a <title> element

High

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

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Document doesn't have a <title> element

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

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Byo2.com 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 Byo2.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

byo2.com

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

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

index.php

common.js

tj.js

01smt.js

smt_data.php

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

index.php

common.js

tj.js

01smt.js

smt_data.php

21409827.js

hm.js

www.2022mry-01.cc

bootstrap.min.css

home.js

jquery.js

swiper.min.css

style.css

white.css

mm-content.css

21056987.js

wq56.js

960x80x.gif

vip90.gif

st.gif

365hengban.gif

3.gif

640-200.gif

0

xincha.gif

20220601-%E9%AA%9E%E5%9E%AE%E6%86%A1%E9%8D%A5%E7%B7%84.gif

12hj3zm.gif

839b34546498487dee53bded5e8ab6727144.gif

0106t120009i751ymA6F4.gif

u=1990099664,1930429746&fm=253&fmt=auto&app=138&f=JPEG

u=767724417,3711498503&fm=253&fmt=auto&app=138&f=JPEG

u=1427949194,1450333609&fm=253&fmt=auto&app=138&f=PNG

202206181655547114.gif

91cy-20220310.gif

frfgges.gif

ky66666.gif

smtlogo.png

1.gif

8.gif

2.gif

7.gif

sdd.jpg

6.gif

qqc.webp