Tools & Wizards About Us
xmzfw.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

xmzfw.com

欢迎访问海纳百川,有容乃大;网站正在思考xmdomain

Page Load Speed

14.5 sec in total

First Response

103 ms

Resources Loaded

13.4 sec

Page Rendered

1.1 sec

xmzfw.com screenshot

About Website

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

海纳百川,有容乃大;xmdomain,website is under construction.

Visit xmzfw.com

Key Findings

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

Performance Metrics

xmzfw.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value25.9 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

xmzfw.com

103 ms

www.xmzfw.com

125 ms

jquery.min.js

63 ms

swiper-bundle.min.css

142 ms

css.css

163 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 24% of them (18 requests) were addressed to the original Xmzfw.com, 72% (54 requests) were made to Yyxy.njau.edu.cn and 1% (1 request) were made to 3152018.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Yyxy.njau.edu.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 815.9 kB (6%)

Content Size

12.6 MB

After Optimization

11.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Xmzfw.com main page is 12.6 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 12.5 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 17.5 kB

  • Original 24.3 kB
  • After minification 24.1 kB
  • After compression 6.8 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 17.5 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 797.6 kB

  • Original 12.5 MB
  • After minification 11.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. Xmzfw images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 798 B

  • Original 3.3 kB
  • After minification 3.3 kB
  • After compression 2.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 798 B or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (36%)

Requests Now

45

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xmzfw.com

xmzfw.com

103 ms

www.xmzfw.com

www.xmzfw.com

125 ms

jquery.min.js

jquery.min.js

63 ms

swiper-bundle.min.css

swiper-bundle.min.css

142 ms

css.css

css.css

163 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

175 ms

_sitegray_d.css

_sitegray_d.css

108 ms

_sitegray.js

_sitegray.js

108 ms

index.vsb.css

index.vsb.css

116 ms

counter.js

counter.js

155 ms

dynclicks.js

dynclicks.js

156 ms

openlink.js

openlink.js

162 ms

base64.js

base64.js

186 ms

formfunc.js

formfunc.js

202 ms

swiper-bundle.min.js

swiper-bundle.min.js

306 ms

centerCutImg.js

centerCutImg.js

210 ms

ajax.js

ajax.js

215 ms

global.js

global.js

196 ms

sj.js

sj.js

1515 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

4 ms

logo.png

logo.png

1763 ms

ss2.png

ss2.png

1952 ms

wap-nav.png

wap-nav.png

2135 ms

15.png

15.png

2153 ms

17.png

17.png

2171 ms

push.js

push.js

745 ms

18.png

18.png

2140 ms

16.png

16.png

2128 ms

logo2.png

logo2.png

2127 ms

yyxy-ewm.png

yyxy-ewm.png

2273 ms

arrow8.png

arrow8.png

2299 ms

zsl.jpg

zsl.jpg

2300 ms

0.jpg

0.jpg

2292 ms

20221114-2.jpg

20221114-2.jpg

2291 ms

20221114-3.jpg

20221114-3.jpg

2274 ms

20221114-4.jpg

20221114-4.jpg

2410 ms

20221114-5.jpg

20221114-5.jpg

2430 ms

arrow1.png

arrow1.png

2452 ms

29286686C8D321FD07EC08F4B16_8517852B_20528.jpg

29286686C8D321FD07EC08F4B16_8517852B_20528.jpg

2451 ms

5D2B0205C4D613639F8ECE8A818_DCBA87C9_41401.jpg

5D2B0205C4D613639F8ECE8A818_DCBA87C9_41401.jpg

2436 ms

D31B308FD2EB24CAE86701F359A_297B922B_1BDC2.jpg

D31B308FD2EB24CAE86701F359A_297B922B_1BDC2.jpg

2436 ms

arrow6.png

arrow6.png

2539 ms

arrow7.png

arrow7.png

2572 ms

5EA3F6EB2B7517E2E245FA2C7C7_08F22267_D462.jpg

5EA3F6EB2B7517E2E245FA2C7C7_08F22267_D462.jpg

2611 ms

88BDF6F03C2CB712293B813A2A2_A1A73624_DDCC.jpg

88BDF6F03C2CB712293B813A2A2_A1A73624_DDCC.jpg

2597 ms

4F005803F4082BC1D8067D15C00_37DE846A_F21B.jpg

4F005803F4082BC1D8067D15C00_37DE846A_F21B.jpg

2597 ms

F599B645A6C1FF9847E745EB908_17A3484D_6EC136.jpg

F599B645A6C1FF9847E745EB908_17A3484D_6EC136.jpg

2583 ms

logo3.png

logo3.png

2673 ms

logo.png

logo.png

1054 ms

ss2.png

ss2.png

975 ms

wap-nav.png

wap-nav.png

806 ms

15.png

15.png

826 ms

16.png

16.png

812 ms

17.png

17.png

841 ms

logo2.png

logo2.png

849 ms

18.png

18.png

946 ms

yyxy-ewm.png

yyxy-ewm.png

1564 ms

arrow8.png

arrow8.png

833 ms

zsl.jpg

zsl.jpg

2068 ms

0.jpg

0.jpg

1883 ms

20221114-3.jpg

20221114-3.jpg

1905 ms

20221114-2.jpg

20221114-2.jpg

2071 ms

20221114-4.jpg

20221114-4.jpg

1712 ms

20221114-5.jpg

20221114-5.jpg

2292 ms

arrow1.png

arrow1.png

1854 ms

29286686C8D321FD07EC08F4B16_8517852B_20528.jpg

29286686C8D321FD07EC08F4B16_8517852B_20528.jpg

2094 ms

5D2B0205C4D613639F8ECE8A818_DCBA87C9_41401.jpg

5D2B0205C4D613639F8ECE8A818_DCBA87C9_41401.jpg

2118 ms

D31B308FD2EB24CAE86701F359A_297B922B_1BDC2.jpg

D31B308FD2EB24CAE86701F359A_297B922B_1BDC2.jpg

2267 ms

arrow6.png

arrow6.png

1948 ms

arrow7.png

arrow7.png

1895 ms

5EA3F6EB2B7517E2E245FA2C7C7_08F22267_D462.jpg

5EA3F6EB2B7517E2E245FA2C7C7_08F22267_D462.jpg

2239 ms

88BDF6F03C2CB712293B813A2A2_A1A73624_DDCC.jpg

88BDF6F03C2CB712293B813A2A2_A1A73624_DDCC.jpg

2279 ms

4F005803F4082BC1D8067D15C00_37DE846A_F21B.jpg

4F005803F4082BC1D8067D15C00_37DE846A_F21B.jpg

2302 ms

F599B645A6C1FF9847E745EB908_17A3484D_6EC136.jpg

F599B645A6C1FF9847E745EB908_17A3484D_6EC136.jpg

3384 ms

logo3.png

logo3.png

2323 ms

Accessibility Review

xmzfw.com accessibility score

69

Accessibility Issues

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

xmzfw.com best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

xmzfw.com SEO score

85

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

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

xmzfw.com

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