Tools & Wizards About Us
evergreen-jp.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

evergreen-jp.net

世界杯买球正规平台 - 2022世界杯买球正规平台

Page Load Speed

7.2 sec in total

First Response

596 ms

Resources Loaded

6.2 sec

Page Rendered

336 ms

evergreen-jp.net screenshot

About Website

Welcome to evergreen-jp.net homepage info - get ready to check Evergreen Jp best content right away, or after learning these important things about evergreen-jp.net

世界杯买球正规平台成立于2016年，我们以“和争共达；合竞共赢”的理念整合云南演出行业资源，致力云南演艺行业发展。2022世界杯买球正规平台具备十多年的演艺策划经验，有专业的舞台搭建、舞美设计团队，是云南首家整合了演艺行业为演艺策划、庆典活动策划提供一条龙服务的演艺公司。世界杯买球正规平台主要以整合云南演艺资源、设备、文化活动和云南演艺公司、云南舞台搭建、云南庆典公司为主体，自2022世界杯买球正...

Visit evergreen-jp.net

Key Findings

We analyzed Evergreen-jp.net page load time and found that the first response time was 596 ms and then it took 6.6 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

evergreen-jp.net performance score

0

Network Requests Diagram

evergreen-jp.net

596 ms

www.evergreen-jp.net

1565 ms

reset.css

381 ms

cmn.css

1292 ms

jquery.lightbox.css

786 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 65% of them (79 requests) were addressed to the original Evergreen-jp.net, 12% (14 requests) were made to Maps.googleapis.com and 6% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Evergreen-jp.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 779.3 kB (28%)

Content Size

2.8 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 21.2 kB

  • Original 28.8 kB
  • After minification 26.9 kB
  • After compression 7.6 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 21.2 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 85.5 kB

  • Original 1.8 MB
  • After minification 1.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. Evergreen Jp images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 643.6 kB

  • Original 956.1 kB
  • After minification 930.8 kB
  • After compression 312.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 643.6 kB or 67% of the original size.

CSS Optimization

-79%

Potential reduce by 29.0 kB

  • Original 36.9 kB
  • After minification 30.4 kB
  • After compression 7.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. Evergreen-jp.net needs all CSS files to be minified and compressed as it can save up to 29.0 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (39%)

Requests Now

112

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

evergreen-jp.net

evergreen-jp.net

596 ms

www.evergreen-jp.net

www.evergreen-jp.net

1565 ms

reset.css

reset.css

381 ms

cmn.css

cmn.css

1292 ms

jquery.lightbox.css

jquery.lightbox.css

786 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1349 ms

jquery.lightbox.js

jquery.lightbox.js

1309 ms

smoothscroll.js

smoothscroll.js

572 ms

tab_switch.js

tab_switch.js

968 ms

jquery.socialbutton.js

jquery.socialbutton.js

780 ms

mootools.js

mootools.js

1163 ms

swfobject.js

swfobject.js

1171 ms

videobox.js

videobox.js

1160 ms

videobox.css

videobox.css

1298 ms

smart_link_from_pc.js

smart_link_from_pc.js

1344 ms

all.js

all.js

271 ms

header_contact.png

header_contact.png

198 ms

header_btn1.png

header_btn1.png

198 ms

header_btn2.png

header_btn2.png

185 ms

header_btn3.png

header_btn3.png

198 ms

header_btn4.png

header_btn4.png

190 ms

logo.png

logo.png

213 ms

main.png

main.png

2760 ms

youtube.png

youtube.png

1134 ms

n1.png

n1.png

383 ms

n2.png

n2.png

393 ms

n3.png

n3.png

392 ms

n4.png

n4.png

406 ms

n5.png

n5.png

568 ms

n6.png

n6.png

581 ms

n7.png

n7.png

580 ms

side_moji1.png

side_moji1.png

608 ms

side_n1_1.png

side_n1_1.png

757 ms

side_n1_2.png

side_n1_2.png

765 ms

side_n1_3.png

side_n1_3.png

760 ms

side_n1_4.png

side_n1_4.png

800 ms

side_n1_5.png

side_n1_5.png

944 ms

side_n1_6.png

side_n1_6.png

948 ms

side_n1_7.png

side_n1_7.png

950 ms

side_n1_8.png

side_n1_8.png

996 ms

side_n1_9.png

side_n1_9.png

1128 ms

side_bn1.png

side_bn1.png

1502 ms

side_n2_1.png

side_n2_1.png

1137 ms

side_n2_2.png

side_n2_2.png

1216 ms

side_n2_3.png

side_n2_3.png

1341 ms

side_n2_4.png

side_n2_4.png

1324 ms

side_n2_5.png

side_n2_5.png

1355 ms

side_n2_6.png

side_n2_6.png

1416 ms

side_img1.png

side_img1.png

1516 ms

side_img2.png

side_img2.png

1526 ms

side_moji3.png

side_moji3.png

1540 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

39 ms

vid_inner.js

vid_inner.js

1597 ms

adobe.png

adobe.png

1528 ms

index_bn1.png

index_bn1.png

2093 ms

index_moji1.png

index_moji1.png

1528 ms

index_bn2.png

index_bn2.png

1546 ms

index_bn3.png

index_bn3.png

1844 ms

index_bn4.png

index_bn4.png

1665 ms

62 ms

xd_arbiter.php

xd_arbiter.php

229 ms

xd_arbiter.php

xd_arbiter.php

436 ms

index_moji8.png

index_moji8.png

1563 ms

kuwashiku1.png

kuwashiku1.png

1555 ms

index_moji2.png

index_moji2.png

1687 ms

index_img1.png

index_img1.png

1891 ms

index_img2.png

index_img2.png

1586 ms

index_moji3.png

index_moji3.png

1653 ms

index_moji4.png

index_moji4.png

1659 ms

index_img3.png

index_img3.png

1727 ms

kuwashiku2.png

kuwashiku2.png

1678 ms

index_moji5.png

index_moji5.png

1668 ms

index_img4.png

index_img4.png

1718 ms

index_moji6.png

index_moji6.png

1680 ms

subete.png

subete.png

1587 ms

footer_logo.png

footer_logo.png

1656 ms

footer_contents.png

footer_contents.png

1674 ms

embed

embed

125 ms

headerbg.png

headerbg.png

1035 ms

underbg.png

underbg.png

1037 ms

menu_bg.png

menu_bg.png

1088 ms

side_arrow1.png

side_arrow1.png

1156 ms

q.png

q.png

1196 ms

ga.js

ga.js

7 ms

mainbg.png

mainbg.png

1187 ms

analytics.js

analytics.js

20 ms

__utm.gif

__utm.gif

15 ms

collect

collect

11 ms

js

js

77 ms

init_embed.js

init_embed.js

42 ms

common.js

common.js

50 ms

map.js

map.js

50 ms

google4.png

google4.png

71 ms

overlay.js

overlay.js

69 ms

util.js

util.js

108 ms

onion.js

onion.js

67 ms

search_impl.js

search_impl.js

101 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

260 ms

stats.js

stats.js

109 ms

openhand_8_8.cur

openhand_8_8.cur

74 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

63 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

89 ms

kh

kh

124 ms

transparent.png

transparent.png

45 ms

controls.js

controls.js

29 ms

vt

vt

143 ms

vt

vt

121 ms

vt

vt

133 ms

vt

vt

151 ms

css

css

81 ms

entity11.png

entity11.png

42 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

31 ms

mapcnt6.png

mapcnt6.png

29 ms

tmapctrl.png

tmapctrl.png

32 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

23 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

29 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

31 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

38 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

14 ms

print.css

print.css

196 ms

collect

collect

4 ms

SEO Factors

evergreen-jp.net SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Evergreen-jp.net 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 Japanese language. Our system also found out that Evergreen-jp.net 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

evergreen-jp.net

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