Tools & Wizards About Us
yankon.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

yankon.com

阳光照明 让世界更明亮

Page Load Speed

36.6 sec in total

First Response

2.2 sec

Resources Loaded

33.9 sec

Page Rendered

550 ms

yankon.com screenshot

About Website

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

浙江阳光照明电器集团股份有限公司创建于1975年，前身系上虞灯泡厂，1996年改为股份有限公司，2000年7月，“阳光照明”A股在上海证券交易所挂牌上市。浙江阳光照明电器集团股份公司是国家级重点高新技术企业、国家大型企业，同时阳光照明已被列为国家300家重点企业及浙江省重点扶持的大企业集团，国家级重合同、守信用单位。

Visit yankon.com

Key Findings

We analyzed Yankon.com page load time and found that the first response time was 2.2 sec and then it took 34.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 24 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

yankon.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.678

8/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

Network Requests Diagram

yankon.com

2155 ms

jquery.min.js

2236 ms

pingzi_video.js

419 ms

common.css

420 ms

bootstrap.css

3031 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 54% of them (57 requests) were addressed to the original Yankon.com, 29% (31 requests) were made to Ykf-webchat.7moor.com and 10% (11 requests) were made to At2020.oss-cn-hangzhou.aliyuncs.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Yankon.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 162.9 kB (3%)

Content Size

5.3 MB

After Optimization

5.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 101.5 kB

  • Original 117.9 kB
  • After minification 88.5 kB
  • After compression 16.5 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 29.4 kB, which is 25% 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 101.5 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 19.1 kB

  • Original 4.7 MB
  • After minification 4.7 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. Yankon images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 34.5 kB

  • Original 396.6 kB
  • After minification 396.6 kB
  • After compression 362.1 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

-12%

Potential reduce by 7.8 kB

  • Original 67.1 kB
  • After minification 67.1 kB
  • After compression 59.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. Yankon.com needs all CSS files to be minified and compressed as it can save up to 7.8 kB or 12% of the original size.

Requests Breakdown

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

Requests Now

74

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yankon.com

yankon.com

2155 ms

jquery.min.js

jquery.min.js

2236 ms

pingzi_video.js

pingzi_video.js

419 ms

common.css

common.css

420 ms

bootstrap.css

bootstrap.css

3031 ms

style.css

style.css

1666 ms

swiper.css

swiper.css

1670 ms

font-awesome.css

font-awesome.css

1899 ms

styles.css

styles.css

1876 ms

7moorInit.js

7moorInit.js

1548 ms

layer.css

layer.css

887 ms

layer.js

layer.js

2145 ms

jsAddress.js

jsAddress.js

1512 ms

base64.js

base64.js

1132 ms

md5.js

md5.js

1361 ms

public.js

public.js

1447 ms

swiper.js

swiper.js

7172 ms

main.js

main.js

1432 ms

jquery.countup.min.js

jquery.countup.min.js

1499 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

2246 ms

bd.png

bd.png

919 ms

hg.png

hg.png

968 ms

f.png

f.png

909 ms

yj.png

yj.png

1012 ms

dh.png

dh.png

965 ms

ewm3.jpg

ewm3.jpg

986 ms

an.png

an.png

1147 ms

logoh1.png

logoh1.png

1338 ms

nav.jpg

nav.jpg

211 ms

tianmao-h.png

tianmao-h.png

308 ms

logoh1.jpg

logoh1.jpg

3633 ms

add.png

add.png

419 ms

jian.png

jian.png

516 ms

20200806134257_9539.jpg

20200806134257_9539.jpg

17515 ms

20200806134530_2009.jpg

20200806134530_2009.jpg

12426 ms

20200806134538_3825.jpg

20200806134538_3825.jpg

17047 ms

20200806134545_2780.jpg

20200806134545_2780.jpg

16297 ms

yg.gif

yg.gif

19568 ms

20240123170400_1951.png

20240123170400_1951.png

19568 ms

20240123170449_5017.png

20240123170449_5017.png

19571 ms

20240123170654_6207.png

20240123170654_6207.png

19572 ms

20200820170647_3591.jpg

20200820170647_3591.jpg

19331 ms

20200810110353_0974.jpg

20200810110353_0974.jpg

19572 ms

20200928151915_2573.png

20200928151915_2573.png

19572 ms

20200928151925_5072.png

20200928151925_5072.png

19572 ms

20200820170656_0339.jpg

20200820170656_0339.jpg

19572 ms

20200810110453_1883.jpg

20200810110453_1883.jpg

19572 ms

tu041.jpg

tu041.jpg

19573 ms

20200810110510_9299.jpg

20200810110510_9299.jpg

19573 ms

d-logo.png

d-logo.png

19573 ms

20230719093834_1966.jpg

20230719093834_1966.jpg

19573 ms

tel.png

tel.png

19572 ms

kefu.png

kefu.png

19573 ms

gzh_qr1.png

gzh_qr1.png

19573 ms

wx.png

wx.png

19573 ms

jiany.png

jiany.png

19573 ms

apply.png

apply.png

19573 ms

gotop.png

gotop.png

19572 ms

banner1.jpg

banner1.jpg

2253 ms

banner.jpg

banner.jpg

2417 ms

banner3.jpg

banner3.jpg

2418 ms

banner4.jpg

banner4.jpg

2356 ms

about.png

about.png

19564 ms

nbg.png

nbg.png

19564 ms

online

online

323 ms

z_stat.php

z_stat.php

1035 ms

DIN%20REGULAR.OTF

DIN%20REGULAR.OTF

20311 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

20358 ms

20200820163359_0447.jpg

20200820163359_0447.jpg

20262 ms

QiMoIMSDK-0564057a6c.js

QiMoIMSDK-0564057a6c.js

536 ms

agentLogo.png

agentLogo.png

294 ms

chatStyle-e5ac22f12b.css

chatStyle-e5ac22f12b.css

591 ms

896beb70-d81a-11e7-b6e7-9da891414b0f.png

896beb70-d81a-11e7-b6e7-9da891414b0f.png

1265 ms

1.png

1.png

883 ms

invite-close.png

invite-close.png

1101 ms

defaultPhoto.png

defaultPhoto.png

1654 ms

small.png

small.png

1102 ms

big.png

big.png

1137 ms

close.png

close.png

1060 ms

moor_chat.html

moor_chat.html

1419 ms

stat.htm

stat.htm

1579 ms

c.js

c.js

1015 ms

moor_style-ff9e5d319b.css

moor_style-ff9e5d319b.css

546 ms

idangerous_swiper-9998bd2b30.css

idangerous_swiper-9998bd2b30.css

297 ms

iconfont.css

iconfont.css

294 ms

m7AllQuote.js

m7AllQuote.js

358 ms

jdate.js

jdate.js

305 ms

distpicker.data.js

distpicker.data.js

827 ms

distpicker.js

distpicker.js

584 ms

idangerous_swiper.js

idangerous_swiper.js

845 ms

base64.min.js

base64.min.js

612 ms

fileTypeMap.js

fileTypeMap.js

750 ms

swiper-bundle.min.js

swiper-bundle.min.js

1091 ms

pic.gif

pic.gif

1104 ms

stat.htm

stat.htm

797 ms

layer.css

layer.css

17481 ms

left_float_icon.png

left_float_icon.png

306 ms

right_float_icon.png

right_float_icon.png

294 ms

continue-advisory.png

continue-advisory.png

292 ms

close-icon.png

close-icon.png

302 ms

video-invite.png

video-invite.png

312 ms

socket.io-2.3.0.js

socket.io-2.3.0.js

546 ms

iconfont.woff

iconfont.woff

327 ms

7moorChat-dfa024282e.js

7moorChat-dfa024282e.js

1070 ms

chat

chat

550 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

9567 ms

Accessibility Review

yankon.com accessibility score

73

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

yankon.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

yankon.com SEO score

92

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

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

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

yankon.com

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