Tools & Wizards About Us
360ublog.com screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

360ublog.com

必博(中国)Bibo·官方网站

Page Load Speed

30.3 sec in total

First Response

15.1 sec

Resources Loaded

15.2 sec

Page Rendered

97 ms

360ublog.com screenshot

About Website

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

必博bibo,安徽必博bibo集团控股有限公司是一家致力于传统能源和新能源以及煤化工产业投资的综合性企业。

Visit 360ublog.com

Key Findings

We analyzed 360ublog.com page load time and found that the first response time was 15.1 sec and then it took 15.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

360ublog.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

360ublog.com

15078 ms

cloudflare.min.js

19 ms

cf.errors.css

3 ms

zepto.min.js

7 ms

cf.common.js

10 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 75% of them (9 requests) were addressed to the original 360ublog.com, 17% (2 requests) were made to Google-analytics.com and 8% (1 request) were made to Ajax.cloudflare.com. The less responsive or slowest element that took the longest time to load (15.1 sec) belongs to the original domain 360ublog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.4 kB (50%)

Content Size

101.8 kB

After Optimization

51.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 360ublog.com main page is 101.8 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. 25% of websites need less resources to load. Javascripts take 48.1 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 5.5 kB

  • Original 8.3 kB
  • After minification 7.7 kB
  • After compression 2.8 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 5.5 kB or 66% of the original size.

Image Optimization

-10%

Potential reduce by 1.7 kB

  • Original 16.1 kB
  • After minification 14.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. 360 Ublog images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 18.8 kB

  • Original 48.1 kB
  • After minification 47.0 kB
  • After compression 29.3 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 18.8 kB or 39% of the original size.

CSS Optimization

-83%

Potential reduce by 24.4 kB

  • Original 29.3 kB
  • After minification 29.2 kB
  • After compression 4.9 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. 360ublog.com needs all CSS files to be minified and compressed as it can save up to 24.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (43%)

Requests Now

7

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

360ublog.com

360ublog.com

15078 ms

cloudflare.min.js

cloudflare.min.js

19 ms

cf.errors.css

cf.errors.css

3 ms

zepto.min.js

zepto.min.js

7 ms

cf.common.js

cf.common.js

10 ms

ga.js

ga.js

6 ms

error_icons.png

error_icons.png

57 ms

__utm.gif

__utm.gif

14 ms

opensans-400.woff

opensans-400.woff

4 ms

opensans-300.woff

opensans-300.woff

3 ms

opensans-600.woff

opensans-600.woff

7 ms

opensans-700.woff

opensans-700.woff

7 ms

Accessibility Review

360ublog.com accessibility score

69

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

360ublog.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

360ublog.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 360ublog.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), while the claimed language is English. Our system also found out that 360ublog.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

360ublog.com

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