Tools & Wizards About Us
edelweiza.com screenshot

Report Summary

  • 0

    Performance

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

edelweiza.com

中国移动官方网站站点详情数据-网站导航

Page Load Speed

4.2 sec in total

First Response

576 ms

Resources Loaded

3 sec

Page Rendered

659 ms

edelweiza.com screenshot

About Website

Visit edelweiza.com now to see the best up-to-date Edelweiza content and also check out these interesting facts you probably never knew about edelweiza.com

中国移动官方网站网站导航大全收集站点详情数据是针对上网用户开发的免费网站导航、分类网站导航平台，一键查找网站，中国移动官方网站让找站变得简单。

Visit edelweiza.com

Key Findings

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

Performance Metrics

edelweiza.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

www.edelweiza.com

576 ms

style.css

159 ms

show_ads.js

7 ms

brand

24 ms

brand

71 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Edelweiza.com, 18% (20 requests) were made to Um.simpli.fi and 10% (11 requests) were made to Tags.bluekai.com. The less responsive or slowest element that took the longest time to load (576 ms) belongs to the original domain Edelweiza.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.4 kB (57%)

Content Size

244.9 kB

After Optimization

104.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Edelweiza.com main page is 244.9 kB. 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 97.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 47.9 kB

  • Original 63.0 kB
  • After minification 60.7 kB
  • After compression 15.1 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 47.9 kB or 76% of the original size.

Image Optimization

-50%

Potential reduce by 48.7 kB

  • Original 97.0 kB
  • After minification 48.4 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. Obviously, Edelweiza needs image optimization as it can save up to 48.7 kB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-41%

Potential reduce by 25.2 kB

  • Original 62.0 kB
  • After minification 60.1 kB
  • After compression 36.8 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 25.2 kB or 41% of the original size.

CSS Optimization

-82%

Potential reduce by 18.7 kB

  • Original 22.8 kB
  • After minification 16.0 kB
  • After compression 4.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. Edelweiza.com needs all CSS files to be minified and compressed as it can save up to 18.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (67%)

Requests Now

78

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.edelweiza.com

www.edelweiza.com

576 ms

style.css

style.css

159 ms

show_ads.js

show_ads.js

7 ms

brand

brand

24 ms

brand

brand

71 ms

classic.js

classic.js

29 ms

counter.asp

counter.asp

6 ms

ca-pub-0051898828821776.js

ca-pub-0051898828821776.js

260 ms

zrt_lookup.html

zrt_lookup.html

254 ms

show_ads_impl.js

show_ads_impl.js

105 ms

getpr.php

getpr.php

235 ms

breadwinnerblog

breadwinnerblog

197 ms

Blogapalooza-community-125x125.jpg

Blogapalooza-community-125x125.jpg

195 ms

10301849144_109b848c6f_o.png

10301849144_109b848c6f_o.png

354 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

257 ms

meter.asp

meter.asp

176 ms

analytics.js

analytics.js

270 ms

mpp.vindicosuite.com

mpp.vindicosuite.com

195 ms

ads

ads

441 ms

125 ms

157 ms

osd.js

osd.js

102 ms

ads

ads

387 ms

ads

ads

411 ms

wordpress.png

wordpress.png

119 ms

meter.asp

meter.asp

53 ms

0

0

97 ms

dpx.js

dpx.js

29 ms

tc.js

tc.js

27 ms

tpid=1DE70445A260E9562203B035025C14AF

tpid=1DE70445A260E9562203B035025C14AF

38 ms

p

p

49 ms

p

p

60 ms

45 ms

blank.gif

blank.gif

81 ms

activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=1487499608

activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=1487499608

19 ms

activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=1487499608

activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=1487499608

21 ms

activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=1487499608

activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=1487499608

38 ms

activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=1487499608

activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=1487499608

41 ms

0

0

13 ms

dpx

dpx

5 ms

aol

aol

48 ms

v2

v2

61 ms

mapuser

mapuser

7 ms

dpx

dpx

82 ms

16090629580330721307

16090629580330721307

125 ms

abg.js

abg.js

237 ms

m_js_controller.js

m_js_controller.js

167 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

502 ms

y_match

y_match

52 ms

11013171514368029633

11013171514368029633

282 ms

27519

27519

401 ms

29931

29931

358 ms

favicon

favicon

333 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

270 ms

s

s

174 ms

x_button_blue2.png

x_button_blue2.png

173 ms

xrefid.xgi

xrefid.xgi

138 ms

pixel

pixel

102 ms

generic

generic

74 ms

i.match

i.match

213 ms

match_redirect

match_redirect

59 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

38 ms

generic

generic

29 ms

1407

1407

147 ms

2964

2964

123 ms

2981

2981

116 ms

tpid=DA29559EA260E9561271F9A802DC16A8

tpid=DA29559EA260E9561271F9A802DC16A8

114 ms

5386

5386

135 ms

3085

3085

74 ms

2831

2831

79 ms

event

event

21 ms

i.match

i.match

91 ms

lr

lr

56 ms

52154.gif

52154.gif

58 ms

4470

4470

75 ms

4448

4448

27 ms

4229

4229

20 ms

lr.gif

lr.gif

7 ms

match_redirect

match_redirect

6 ms

match_redirect

match_redirect

9 ms

sync

sync

13 ms

DA29559EA260E9561271F9A802DC16A8

DA29559EA260E9561271F9A802DC16A8

38 ms

match_redirect

match_redirect

12 ms

ProfilesEngineServlet

ProfilesEngineServlet

28 ms

ProfilesEngineServlet

ProfilesEngineServlet

41 ms

match_redirect

match_redirect

8 ms

21 ms

exelate

exelate

3 ms

spotx_match

spotx_match

5 ms

43 ms

tap.php

tap.php

23 ms

fb_match

fb_match

4 ms

u.php

u.php

14 ms

23 ms

an

an

4 ms

engine

engine

105 ms

lj_match

lj_match

8 ms

cw_match

cw_match

10 ms

rtset

rtset

28 ms

merge

merge

10 ms

rb_match

rb_match

14 ms

ox_match

ox_match

13 ms

pm_match

pm_match

9 ms

tap.php

tap.php

12 ms

Pug

Pug

75 ms

pixel

pixel

44 ms

g_match

g_match

4 ms

match_redirect

match_redirect

5 ms

sd

sd

32 ms

pixel

pixel

32 ms

aa_px

aa_px

4 ms

Accessibility Review

edelweiza.com accessibility score

92

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

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

edelweiza.com SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

edelweiza.com

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