Access evergreen361.com. Evergreen Leather - Professional handbag/wallet/evening bag manufactory from Guangzhou,China

evergreen361.com screenshot

32

Performance

Renders faster than
52% of other websites
61

Accessibility

Visual factors better than
that of 27% of websites
50

Best Practices

More advanced features
available than in
19% of websites
73

SEO

Google-friendlier than
31% of websites

First Response

664 ms

Resources Loaded

22.8 sec

Page Rendered

296 ms

evergreen361.com screenshot

About Website

Click here to check amazing Evergreen 361 content. Otherwise, check out these important facts you probably never knew about evergreen361.com

Evergreen leater Co., Ltd. is one of the leading manufacturers of lady handbag,wallet,evening bag,purse

Visit evergreen361.com

Key Findings

We analyzed Evergreen361.com page load time and found that the first response time was 664 ms and then it took 23.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value43.4 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.158

74/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

evergreen361.com

664 ms

evergreen361.com

1517 ms

jquery.js

481 ms

css.css

692 ms

correctpng.js

688 ms

Our browser made a total of 175 requests to load all elements on the main page. We found that 98% of them (172 requests) were addressed to the original Evergreen361.com, 1% (1 request) were made to Apps.bdimg.com and 1% (1 request) were made to Sdk.51.la. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Apps.bdimg.com.

Content Size

5.1 MB

After Optimization

4.9 MB

In fact, the total size of Evergreen361.com main page is 5.1 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. 50% of websites need less resources to load. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 140.9 kB

Original 155.6 kB
After minification 126.7 kB
After compression 14.7 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 28.9 kB, which is 19% 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 140.9 kB or 91% of the original size.

Image Optimization

-2%

Potential reduce by 74.6 kB

Original 4.9 MB
After minification 4.8 MB

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. Evergreen 361 images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 4.7 kB

Original 68.6 kB
After minification 68.0 kB
After compression 63.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. This website has mostly compressed JavaScripts.

CSS Optimization

-38%

Potential reduce by 1.1 kB

Original 2.8 kB
After minification 2.7 kB
After compression 1.7 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. Evergreen361.com needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 38% of the original size.

Requests Now

172

After Optimization

153

The browser has sent 172 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evergreen 361. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 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 semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Evergreen361.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Evergreen361.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

evergreen361.com

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