Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

Page Load Speed

57.2 sec in total

First Response

9.6 sec

Resources Loaded

47.3 sec

Page Rendered

279 ms

yue368.com screenshot

About Website

Welcome to yue368.com homepage info - get ready to check Yue 368 best content right away, or after learning these important things about yue368.com

Visit yue368.com

Key Findings

We analyzed Yue368.com page load time and found that the first response time was 9.6 sec and then it took 47.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

yue368.com performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

79/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

yue368.com

9633 ms

www.yue368.com

4050 ms

style.css

2542 ms

type-button-1.jpg

719 ms

c.js

1208 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 31% of them (23 requests) were addressed to the original Yue368.com, 13% (10 requests) were made to Bdimg.share.baidu.com and 12% (9 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source T11.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.4 kB (30%)

Content Size

885.4 kB

After Optimization

624.0 kB

In fact, the total size of Yue368.com main page is 885.4 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. Images take 515.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 36.8 kB

  • Original 46.3 kB
  • After minification 46.3 kB
  • After compression 9.5 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 36.8 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 15.6 kB

  • Original 515.9 kB
  • After minification 500.3 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. Yue 368 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 194.8 kB

  • Original 303.6 kB
  • After minification 303.6 kB
  • After compression 108.8 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 194.8 kB or 64% of the original size.

CSS Optimization

-73%

Potential reduce by 14.1 kB

  • Original 19.5 kB
  • After minification 19.0 kB
  • After compression 5.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. Yue368.com needs all CSS files to be minified and compressed as it can save up to 14.1 kB or 73% of the original size.

Requests Breakdown

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

Requests Now

70

After Optimization

49

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

Accessibility Review

yue368.com accessibility score

56

Accessibility Issues

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.

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

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

Image elements do not have [alt] attributes

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

yue368.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

yue368.com SEO score

62

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yue368.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Yue368.com main page’s claimed encoding is gb2312. 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

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