Access 51aimei.com. 无忧爱美网

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

51aimei.com

548 ms

51aimei.com

682 ms

www.51aimei.com

2471 ms

index_v1.css

2197 ms

jquery.min.js

1312 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 31% of them (14 requests) were addressed to the original 51aimei.com, 69% (31 requests) were made to Static.51aimei.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain 51aimei.com.

Content Size

702.2 kB

After Optimization

482.1 kB

In fact, the total size of 51aimei.com main page is 702.2 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. 20% of websites need less resources to load. Images take 414.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 39.5 kB

Original 52.7 kB
After minification 50.1 kB
After compression 13.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 39.5 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 19.8 kB

Original 414.9 kB
After minification 395.1 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. 51 Aimei images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 118.0 kB

Original 181.6 kB
After minification 177.5 kB
After compression 63.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 118.0 kB or 65% of the original size.

CSS Optimization

-81%

Potential reduce by 42.8 kB

Original 53.0 kB
After minification 45.7 kB
After compression 10.2 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. 51aimei.com needs all CSS files to be minified and compressed as it can save up to 42.8 kB or 81% of the original size.

Requests Now

After Optimization

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 51 Aimei. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts 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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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 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

Form elements do not have associated labels

High

Links do not have a discernible name

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

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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

High

Links are not crawlable

Language and Encoding

Language Detected

ZH
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 51aimei.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 51aimei.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

51aimei.com

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

51aimei.com

51aimei.com

www.51aimei.com

index_v1.css

jquery.min.js

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

51aimei.com

51aimei.com

www.51aimei.com

index_v1.css

jquery.min.js

float_qrcode.js

slides.js

dialog.min.js

count.js

20200210053942779.jpg

20220531065418741.jpg

20220208080800916.jpg

20211118070540967.jpg

20211102065551350.jpg

20191024115717332.jpg

20131021101229612.jpg

20190325101922487.jpg

20190325101935396.jpg

20190325101947488.jpg

20190325101956692.jpg

wrap_bgs.jpg

index_repeat.png

bg_new.png

login_bg.gif

logo.gif

nav_repeat.png

nav_on.png

focus_bgs.jpg

pa.gif

cn_tdc.png

ad.jpg

s.gif

aimei_li.gif

focus_c.jpg

hot_news.gif

bgs_new.png

new_li.gif

cst_line.png

cst_bg.png

qam_bg.png

h_bg.jpg

case_bg.png

line.gif