Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

belle.eeeyo.com

没有找到站点

Page Load Speed

31.8 sec in total

First Response

1.6 sec

Resources Loaded

29.6 sec

Page Rendered

600 ms

belle.eeeyo.com screenshot

About Website

Welcome to belle.eeeyo.com homepage info - get ready to check Belle Eeeyo best content right away, or after learning these important things about belle.eeeyo.com

Visit belle.eeeyo.com

Key Findings

We analyzed Belle.eeeyo.com page load time and found that the first response time was 1.6 sec and then it took 30.2 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

belle.eeeyo.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

belle.eeeyo.com

1599 ms

www.eeeyo.com

4973 ms

style_2_common.css

505 ms

common.js

672 ms

portal.js

341 ms

Our browser made a total of 166 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Belle.eeeyo.com, 68% (113 requests) were made to Eeeyo.com and 26% (43 requests) were made to Img01.eeeyo.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Img01.eeeyo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 459.9 kB (18%)

Content Size

2.6 MB

After Optimization

2.1 MB

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

HTML Optimization

-82%

Potential reduce by 85.5 kB

  • Original 104.7 kB
  • After minification 100.9 kB
  • After compression 19.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 85.5 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 154.6 kB

  • Original 2.2 MB
  • After minification 2.0 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. Belle Eeeyo images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 141.9 kB

  • Original 199.5 kB
  • After minification 175.4 kB
  • After compression 57.6 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 141.9 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 77.9 kB

  • Original 97.9 kB
  • After minification 92.3 kB
  • After compression 20.0 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. Belle.eeeyo.com needs all CSS files to be minified and compressed as it can save up to 77.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (31%)

Requests Now

88

After Optimization

61

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

Accessibility Review

belle.eeeyo.com accessibility score

76

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

Best Practices

belle.eeeyo.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

belle.eeeyo.com SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Belle.eeeyo.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 Belle.eeeyo.com main page’s claimed encoding is gbk. 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 Belle Eeeyo. 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: