Tools & Wizards About Us
libo.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

libo.com

丽波日化

Page Load Speed

1.8 sec in total

First Response

417 ms

Resources Loaded

1.2 sec

Page Rendered

176 ms

libo.com screenshot

About Website

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

丽波日化

Visit libo.com

Key Findings

We analyzed Libo.com page load time and found that the first response time was 417 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

libo.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value23.5 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.3

39/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

libo.com

417 ms

public.css

137 ms

mt_style.css

145 ms

style.css

200 ms

southidcj2f.Js

264 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 79.3 kB (27%)

Content Size

289.4 kB

After Optimization

210.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 28.0 kB

  • Original 32.0 kB
  • After minification 26.2 kB
  • After compression 4.0 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. This page needs HTML code to be minified as it can gain 5.9 kB, which is 18% 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 28.0 kB or 88% of the original size.

Image Optimization

-9%

Potential reduce by 19.2 kB

  • Original 216.0 kB
  • After minification 196.8 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. Libo images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 4.6 kB

  • Original 8.5 kB
  • After minification 8.5 kB
  • After compression 3.9 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 4.6 kB or 54% of the original size.

CSS Optimization

-83%

Potential reduce by 27.5 kB

  • Original 32.9 kB
  • After minification 28.1 kB
  • After compression 5.5 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. Libo.com needs all CSS files to be minified and compressed as it can save up to 27.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (28%)

Requests Now

40

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

libo.com

libo.com

417 ms

public.css

public.css

137 ms

mt_style.css

mt_style.css

145 ms

style.css

style.css

200 ms

southidcj2f.Js

southidcj2f.Js

264 ms

css2.css

css2.css

126 ms

css3.css

css3.css

79 ms

css1.css

css1.css

211 ms

bg_all.jpg

bg_all.jpg

76 ms

msn.png

msn.png

86 ms

class1.gif

class1.gif

74 ms

plist.gif

plist.gif

85 ms

class3.gif

class3.gif

142 ms

btn_more.gif

btn_more.gif

142 ms

dot1.gif

dot1.gif

154 ms

2012971758175.jpg

2012971758175.jpg

302 ms

yyri2.gif

yyri2.gif

180 ms

20129717233406.jpg

20129717233406.jpg

355 ms

20129717036635.jpg

20129717036635.jpg

368 ms

20129716594522.jpg

20129716594522.jpg

361 ms

201297165729650.jpg

201297165729650.jpg

318 ms

201297165427322.jpg

201297165427322.jpg

474 ms

201297164914683.jpg

201297164914683.jpg

558 ms

20129515277346.gif

20129515277346.gif

552 ms

20129515247763.gif

20129515247763.gif

543 ms

201295152226775.gif

201295152226775.gif

509 ms

bg_index_title3.jpg

bg_index_title3.jpg

434 ms

bg_index_content3.jpg

bg_index_content3.jpg

501 ms

bg_index_btm3.jpg

bg_index_btm3.jpg

496 ms

bg_index_title4.jpg

bg_index_title4.jpg

516 ms

bg_index_content4.jpg

bg_index_content4.jpg

567 ms

bg_index_btm4.jpg

bg_index_btm4.jpg

559 ms

bg_index_title5.jpg

bg_index_title5.jpg

582 ms

bg_index_content5.jpg

bg_index_content5.jpg

560 ms

bg_index_title1.jpg

bg_index_title1.jpg

579 ms

bg_index_content1.jpg

bg_index_content1.jpg

580 ms

bg_index_btm1.jpg

bg_index_btm1.jpg

630 ms

bg_index_title2.jpg

bg_index_title2.jpg

581 ms

bg_index_content2.jpg

bg_index_content2.jpg

579 ms

bg_index_btm2.jpg

bg_index_btm2.jpg

591 ms

bg_footer.jpg

bg_footer.jpg

593 ms

Accessibility Review

libo.com accessibility score

80

Accessibility Issues

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

libo.com SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 doesn't use legible font sizes

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

libo.com

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