Tools & Wizards About Us
100nz.com screenshot

Report Summary

  • 0

    Performance

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

100nz.com

Page Load Speed

62.1 sec in total

First Response

6.5 sec

Resources Loaded

55.2 sec

Page Rendered

455 ms

100nz.com screenshot

About Website

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

长沙现代女子医院品牌15周年,华中首家女子妇科医院,15年铸就长沙最专业的人流医院,在妇科炎症以及妇科肿瘤诊疗方面积累丰富经验,咨询热线:0731-88688855

Visit 100nz.com

Key Findings

We analyzed 100nz.com page load time and found that the first response time was 6.5 sec and then it took 55.6 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

100nz.com performance score

0

Network Requests Diagram

100nz.com

6472 ms

www.100nz.com

8753 ms

index.css

1356 ms

uaredirect.js

787 ms

untc_topcommon.js

1126 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 73% of them (83 requests) were addressed to the original 100nz.com, 11% (12 requests) were made to Pyt.zoosnet.net and 8% (9 requests) were made to Lxbjs.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain 100nz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 288.9 kB (33%)

Content Size

886.4 kB

After Optimization

597.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 100nz.com main page is 886.4 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. 25% of websites need less resources to load. Images take 643.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 81.8 kB

  • Original 99.9 kB
  • After minification 85.4 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 14.5 kB, which is 15% 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 81.8 kB or 82% of the original size.

Image Optimization

-18%

Potential reduce by 113.8 kB

  • Original 643.2 kB
  • After minification 529.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, 100 Nz needs image optimization as it can save up to 113.8 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 84.6 kB

  • Original 132.1 kB
  • After minification 131.4 kB
  • After compression 47.4 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 84.6 kB or 64% of the original size.

CSS Optimization

-78%

Potential reduce by 8.7 kB

  • Original 11.2 kB
  • After minification 10.1 kB
  • After compression 2.5 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. 100nz.com needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

85

After Optimization

63

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

100nz.com

100nz.com

6472 ms

www.100nz.com

www.100nz.com

8753 ms

index.css

index.css

1356 ms

uaredirect.js

uaredirect.js

787 ms

untc_topcommon.js

untc_topcommon.js

1126 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

5375 ms

banner.js

banner.js

1178 ms

hm.js

hm.js

4566 ms

hm.js

hm.js

8652 ms

hm.js

hm.js

20266 ms

tab.js

tab.js

585 ms

MSClass.js

MSClass.js

1373 ms

ScrollPic.js

ScrollPic.js

2295 ms

LsJS.aspx

LsJS.aspx

7121 ms

untc_utils.js

untc_utils.js

544 ms

api.js

api.js

698 ms

lxb.js

lxb.js

1406 ms

hm.gif

hm.gif

1242 ms

bpa.js

bpa.js

1381 ms

log.gif

log.gif

304 ms

_l.js

_l.js

364 ms

bpaId

bpaId

900 ms

bg.jpg

bg.jpg

486 ms

bg_common.gif

bg_common.gif

558 ms

logo.png

logo.png

3119 ms

top_txt.png

top_txt.png

1239 ms

logo_r_p.png

logo_r_p.png

4195 ms

258x234.jpg

258x234.jpg

14418 ms

foc1.jpg

foc1.jpg

10413 ms

foc2.jpg

foc2.jpg

9259 ms

foc3.jpg

foc3.jpg

6752 ms

foc4.jpg

foc4.jpg

9156 ms

b1.jpg

b1.jpg

7035 ms

b2.jpg

b2.jpg

7743 ms

b3.jpg

b3.jpg

15739 ms

t1.jpg

t1.jpg

8184 ms

js1.jpg

js1.jpg

10652 ms

js2.jpg

js2.jpg

20136 ms

js3.jpg

js3.jpg

14721 ms

js4.jpg

js4.jpg

19457 ms

js5.jpg

js5.jpg

14021 ms

t2.jpg

t2.jpg

15618 ms

dc2.jpg

dc2.jpg

19938 ms

dc4.jpg

dc4.jpg

20134 ms

dc5.jpg

dc5.jpg

18529 ms

dc8.jpg

dc8.jpg

19138 ms

dc3.jpg

dc3.jpg

20135 ms

dc9.jpg

dc9.jpg

20135 ms

ks1.jpg

ks1.jpg

20136 ms

ks2.jpg

ks2.jpg

20139 ms

bk.jpg

bk.jpg

20138 ms

zx.jpg

zx.jpg

20140 ms

ad1.jpg

ad1.jpg

20140 ms

ks3.jpg

ks3.jpg

20140 ms

ks4.jpg

ks4.jpg

20141 ms

ks5.jpg

ks5.jpg

20142 ms

wx.jpg

wx.jpg

20142 ms

wb.jpg

wb.jpg

20143 ms

log.gif

log.gif

301 ms

6.css

6.css

298 ms

map.jpg

map.jpg

19680 ms

g1.jpg

g1.jpg

19600 ms

g2.jpg

g2.jpg

19902 ms

hm.gif

hm.gif

543 ms

g3.jpg

g3.jpg

19869 ms

JS5.aspx

JS5.aspx

2017 ms

g4.jpg

g4.jpg

19946 ms

minvite_cn.png

minvite_cn.png

1606 ms

JS_Float.aspx

JS_Float.aspx

1109 ms

2.png

2.png

350 ms

log.gif

log.gif

347 ms

log.gif

log.gif

715 ms

monline_cn.gif

monline_cn.gif

2336 ms

7.gif

7.gif

1218 ms

g5.jpg

g5.jpg

17932 ms

r1.jpg

r1.jpg

17315 ms

newsid0.aspx

newsid0.aspx

567 ms

r2.jpg

r2.jpg

16638 ms

r3.jpg

r3.jpg

19953 ms

r4.jpg

r4.jpg

19980 ms

r5.jpg

r5.jpg

17324 ms

hz.jpg

hz.jpg

17703 ms

Banner.jpg

Banner.jpg

20484 ms

CheckInvitejs.aspx

CheckInvitejs.aspx

566 ms

940x240.jpg

940x240.jpg

20112 ms

ban2.jpg

ban2.jpg

19724 ms

bgfc.jpg

bgfc.jpg

13865 ms

s2.jpg

s2.jpg

13433 ms

bgb.jpg

bgb.jpg

13781 ms

CheckInvitejs.aspx

CheckInvitejs.aspx

1287 ms

s.jpg

s.jpg

11447 ms

bbg.jpg

bbg.jpg

11450 ms

s3.jpg

s3.jpg

12691 ms

b4.jpg

b4.jpg

12599 ms

bg1.jpg

bg1.jpg

12353 ms

bg3.jpg

bg3.jpg

14017 ms

bg2.jpg

bg2.jpg

12937 ms

left.jpg

left.jpg

12801 ms

right.jpg

right.jpg

12882 ms

s4.jpg

s4.jpg

13258 ms

bg4.jpg

bg4.jpg

13367 ms

s5.jpg

s5.jpg

13392 ms

on.jpg

on.jpg

14896 ms

search.jpg

search.jpg

13874 ms

sbmt.jpg

sbmt.jpg

13870 ms

bg5.jpg

bg5.jpg

14296 ms

act.jpg

act.jpg

14316 ms

s1.jpg

s1.jpg

15149 ms

bg6.jpg

bg6.jpg

16294 ms

CheckInvitejs.aspx

CheckInvitejs.aspx

1213 ms

CheckInvitejs.aspx

CheckInvitejs.aspx

1400 ms

CheckInvitejs.aspx

CheckInvitejs.aspx

524 ms

CheckInvitejs.aspx

CheckInvitejs.aspx

487 ms

Accessibility Review

100nz.com accessibility score

53

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

Document doesn't have a <title> element

High

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

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

Best Practices

100nz.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

100nz.com SEO score

55

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

Document doesn't have a <title> element

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 100nz.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 100nz.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

100nz.com

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