Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

keede.com

可得眼镜网-中国领先的网上眼镜商城_网上配眼镜_隐形眼镜_美瞳彩色隐形眼镜30天无理由退换货保障

Page Load Speed

60.3 sec in total

First Response

1.3 sec

Resources Loaded

57.9 sec

Page Rendered

1.1 sec

keede.com screenshot

About Website

Click here to check amazing Keede content for China. Otherwise, check out these important facts you probably never knew about keede.com

可得网-中国眼镜网络销售NO.1,强生美瞳彩色隐形眼镜,博士伦隐形眼镜官网指定网上配眼镜商城,各大品牌正品近视眼镜框、眼镜架、隐形眼镜及护理液注意事项及评价!支付宝付款,眼镜价格比淘宝网眼镜店更便宜放心

Visit keede.com

Key Findings

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

Performance Metrics

keede.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value30.7 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value7,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value37.9 s

0/100

10%

Network Requests Diagram

keede.com

1335 ms

www.keede.com

4390 ms

p_keede.css

4239 ms

p_allwebsite.css

981 ms

Global

886 ms

Our browser made a total of 177 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Keede.com, 87% (154 requests) were made to Pic.keede.com and 2% (3 requests) were made to Combo.b.qq.com. The less responsive or slowest element that took the longest time to load (18.4 sec) relates to the external source Pic.keede.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 587.4 kB (9%)

Content Size

6.7 MB

After Optimization

6.1 MB

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

HTML Optimization

-84%

Potential reduce by 103.4 kB

  • Original 123.7 kB
  • After minification 111.2 kB
  • After compression 20.2 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 103.4 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 248.5 kB

  • Original 6.2 MB
  • After minification 5.9 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. Keede images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 174.5 kB

  • Original 301.0 kB
  • After minification 289.0 kB
  • After compression 126.5 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 174.5 kB or 58% of the original size.

CSS Optimization

-84%

Potential reduce by 61.0 kB

  • Original 72.4 kB
  • After minification 54.1 kB
  • After compression 11.4 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. Keede.com needs all CSS files to be minified and compressed as it can save up to 61.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (13%)

Requests Now

172

After Optimization

150

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

Accessibility Review

keede.com accessibility score

53

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

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

keede.com best practices score

75

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

SEO Factors

keede.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keede.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 Keede.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

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