Tools & Wizards About Us
awildgreenlife.com screenshot

Report Summary

  • 0

    Performance

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

awildgreenlife.com

亚-搏手机版登录页面界面

Page Load Speed

8.3 sec in total

First Response

1.5 sec

Resources Loaded

5.6 sec

Page Rendered

1.2 sec

awildgreenlife.com screenshot

About Website

Click here to check amazing Awildgreenlife content. Otherwise, check out these important facts you probably never knew about awildgreenlife.com

亚-搏手机版登录页面界面致力于成为受人尊敬和信赖的以环卫机器人为龙头的智能环境装备及服务的行业引领者。亚搏手机登录主页围绕“智慧环卫” 的发展战略，打造“智能装备、智云平台、智慧服务”三大体系，公司业务涵盖环卫装备、环卫机器人、环卫一体化服务、智慧环境管理等各项领域。

Visit awildgreenlife.com

Key Findings

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

Performance Metrics

awildgreenlife.com performance score

0

Network Requests Diagram

awildgreenlife.com

1484 ms

wp-emoji-release.min.js

90 ms

style.min.css

179 ms

styles.css

251 ms

style.css

258 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 67% of them (29 requests) were addressed to the original Awildgreenlife.com, 30% (13 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Awildgreenlife.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (87%)

Content Size

1.8 MB

After Optimization

242.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Awildgreenlife.com main page is 1.8 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. 45% of websites need less resources to load. CSS take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 109.4 kB

  • Original 126.3 kB
  • After minification 114.7 kB
  • After compression 16.9 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 109.4 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 438 B

  • Original 20.2 kB
  • After minification 19.7 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. Awildgreenlife images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 228.3 kB

  • Original 306.2 kB
  • After minification 302.6 kB
  • After compression 77.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 228.3 kB or 75% of the original size.

CSS Optimization

-91%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 1.0 MB
  • After compression 128.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. Awildgreenlife.com needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (64%)

Requests Now

28

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

awildgreenlife.com

awildgreenlife.com

1484 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

90 ms

style.min.css

style.min.css

179 ms

styles.css

styles.css

251 ms

style.css

style.css

258 ms

style.css

style.css

262 ms

css

css

32 ms

style.css

style.css

355 ms

td_legacy_main.css

td_legacy_main.css

624 ms

td_standard_pack_main.css

td_standard_pack_main.css

397 ms

tdb_less_front.css

tdb_less_front.css

595 ms

jquery.js

jquery.js

601 ms

jquery-migrate.min.js

jquery-migrate.min.js

345 ms

front-end-script.js

front-end-script.js

614 ms

scripts.js

scripts.js

609 ms

underscore.min.js

underscore.min.js

830 ms

js_posts_autoload.min.js

js_posts_autoload.min.js

831 ms

tagdiv_theme.min.js

tagdiv_theme.min.js

1009 ms

comment-reply.min.js

comment-reply.min.js

831 ms

js_files_for_front.min.js

js_files_for_front.min.js

831 ms

wp-embed.min.js

wp-embed.min.js

830 ms

A-Wild-green-life-1.png

A-Wild-green-life-1.png

195 ms

Untitled.png

Untitled.png

400 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

205 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

364 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

207 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

206 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

206 ms

mem8YaGs126MiZpBA-UFVZ0d.woff

mem8YaGs126MiZpBA-UFVZ0d.woff

463 ms

mem5YaGs126MiZpBA-UNirkOUuhv.woff

mem5YaGs126MiZpBA-UNirkOUuhv.woff

465 ms

mem5YaGs126MiZpBA-UN7rgOUuhv.woff

mem5YaGs126MiZpBA-UN7rgOUuhv.woff

464 ms

newspaper.woff

newspaper.woff

726 ms

mem6YaGs126MiZpBA-UFUK0Zdcs.woff

mem6YaGs126MiZpBA-UFUK0Zdcs.woff

465 ms

memnYaGs126MiZpBA-UFUKWyV9hrIqU.woff

memnYaGs126MiZpBA-UFUKWyV9hrIqU.woff

464 ms

memnYaGs126MiZpBA-UFUKXGUdhrIqU.woff

memnYaGs126MiZpBA-UFUKXGUdhrIqU.woff

468 ms

KFOkCnqEu92Fr1Mu51xIIzQ.woff

KFOkCnqEu92Fr1Mu51xIIzQ.woff

466 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff

KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff

463 ms

elements.png

elements.png

345 ms

Untitled-2-534x462.png

Untitled-2-534x462.png

351 ms

Untitled-1-533x261.png

Untitled-1-533x261.png

540 ms

Untitled1-533x261.png

Untitled1-533x261.png

436 ms

Untitled-2-324x160.png

Untitled-2-324x160.png

260 ms

Untitled-324x160.jpg

Untitled-324x160.jpg

174 ms

Accessibility Review

awildgreenlife.com accessibility score

53

Accessibility Issues

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

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

awildgreenlife.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

awildgreenlife.com SEO score

83

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

Document doesn't have a <title> element

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

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Awildgreenlife.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Awildgreenlife.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

awildgreenlife.com

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