Tools & Wizards About Us
weimao.com screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

weimao.com

微猫

Page Load Speed

10.4 sec in total

First Response

952 ms

Resources Loaded

9.3 sec

Page Rendered

123 ms

weimao.com screenshot

About Website

Visit weimao.com now to see the best up-to-date Weimao content and also check out these interesting facts you probably never knew about weimao.com

Visit weimao.com

Key Findings

We analyzed Weimao.com page load time and found that the first response time was 952 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

weimao.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

weimao.com

952 ms

www.weimao.com

1307 ms

common.css

455 ms

jquery.min.js

1008 ms

common.js

674 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that all of those requests were addressed to Weimao.com and no external sources were called. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Weimao.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.7 kB (69%)

Content Size

64.7 kB

After Optimization

20.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Weimao.com main page is 64.7 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. Only 5% of websites need less resources to load. CSS take 43.5 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 2.0 kB

  • Original 2.9 kB
  • After minification 2.2 kB
  • After compression 984 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. This page needs HTML code to be minified as it can gain 691 B, which is 23% 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 2.0 kB or 67% of the original size.

Image Optimization

-37%

Potential reduce by 6.8 kB

  • Original 18.2 kB
  • After minification 11.4 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. Obviously, Weimao needs image optimization as it can save up to 6.8 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-83%

Potential reduce by 35.9 kB

  • Original 43.5 kB
  • After minification 40.4 kB
  • After compression 7.6 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. Weimao.com needs all CSS files to be minified and compressed as it can save up to 35.9 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weimao. According to our analytics all requests are already optimized.

Network Requests Diagram

weimao.com

weimao.com

952 ms

www.weimao.com

www.weimao.com

1307 ms

common.css

common.css

455 ms

jquery.min.js

jquery.min.js

1008 ms

common.js

common.js

674 ms

login.js

login.js

912 ms

main_bkg.jpg

main_bkg.jpg

452 ms

login_bkg11.jpg

login_bkg11.jpg

6030 ms

box_bkg.jpg

box_bkg.jpg

3488 ms

Sub-line.jpg

Sub-line.jpg

725 ms

bkg_input.jpg

bkg_input.jpg

760 ms

obtn_bkg.jpg

obtn_bkg.jpg

891 ms

gbtn_bkg.jpg

gbtn_bkg.jpg

1104 ms

xinl.png

xinl.png

1137 ms

qq21.png

qq21.png

2259 ms

renren1.png

renren1.png

1483 ms

footer_bg.jpg

footer_bg.jpg

1516 ms

Accessibility Review

weimao.com accessibility score

59

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

weimao.com best practices score

58

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

weimao.com SEO score

90

Search Engine Optimization Advices

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

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

weimao.com

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