Tools & Wizards About Us
winic.org screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

winic.org

吉信通|中正云通信|世纪中正|短信平台|短信接口|验证码|国际短信-20年专注企业通信解决方案，因您而变！

Page Load Speed

10 sec in total

First Response

1.1 sec

Resources Loaded

8.6 sec

Page Rendered

306 ms

winic.org screenshot

About Website

Visit winic.org now to see the best up-to-date Winic content for China and also check out these interesting facts you probably never knew about winic.org

中正云通信-吉信通拥有强大的服务与技术团队，20年云通信行业经验，根据您的需求个性订制，为您提供短信、云语音、400电话.....

Visit winic.org

Key Findings

We analyzed Winic.org page load time and found that the first response time was 1.1 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

winic.org performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

winic.org

1146 ms

css.css

414 ms

index.css

621 ms

animate.min.css

638 ms

jquery-1.7.2.min.js

1349 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 64% of them (58 requests) were addressed to the original Winic.org, 8% (7 requests) were made to Ckmap.mediav.com and 5% (5 requests) were made to S.union.360.cn. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Hm.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 212.9 kB (11%)

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Winic.org main page is 1.9 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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 38.1 kB

  • Original 49.4 kB
  • After minification 40.4 kB
  • After compression 11.4 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 9.1 kB, which is 18% 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 38.1 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 157.6 kB

  • Original 1.6 MB
  • After minification 1.4 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. Winic images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 16.2 kB

  • Original 272.1 kB
  • After minification 266.6 kB
  • After compression 255.9 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 1.1 kB

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

Requests Breakdown

Number of requests can be reduced by 24 (30%)

Requests Now

81

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

winic.org

winic.org

1146 ms

css.css

css.css

414 ms

index.css

index.css

621 ms

animate.min.css

animate.min.css

638 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1349 ms

dgheader.mini.js

dgheader.mini.js

1436 ms

banner.css

banner.css

415 ms

superslide.2.1.js

superslide.2.1.js

418 ms

SuperSlide2.js

SuperSlide2.js

624 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

8 ms

govicons.js

govicons.js

1362 ms

logo.png

logo.png

215 ms

tel2.png

tel2.png

417 ms

winic01.jpg

winic01.jpg

2266 ms

bt1.png

bt1.png

212 ms

bt2.png

bt2.png

222 ms

bt3.png

bt3.png

238 ms

dxt.jpg

dxt.jpg

1047 ms

gla.png

gla.png

419 ms

glb.png

glb.png

442 ms

lxkf.jpg

lxkf.jpg

472 ms

yya.png

yya.png

623 ms

yyb.png

yyb.png

627 ms

wla.png

wla.png

664 ms

wlb.png

wlb.png

706 ms

bba.png

bba.png

830 ms

bbb.png

bbb.png

834 ms

jda.png

jda.png

885 ms

jdb.png

jdb.png

943 ms

gdgl.png

gdgl.png

1037 ms

h1.jpg

h1.jpg

1042 ms

h2.jpg

h2.jpg

1106 ms

h3.jpg

h3.jpg

1176 ms

h4.jpg

h4.jpg

1244 ms

h5.jpg

h5.jpg

1249 ms

h6.jpg

h6.jpg

1255 ms

h7.jpg

h7.jpg

1327 ms

h8.jpg

h8.jpg

1411 ms

hb9.jpg

hb9.jpg

1451 ms

hb10.jpg

hb10.jpg

1456 ms

l1.png

l1.png

1464 ms

l2.png

l2.png

1547 ms

l3.png

l3.png

1644 ms

l4.png

l4.png

1658 ms

gst.jpg

gst.jpg

2079 ms

1.png

1.png

1673 ms

hm.js

hm.js

2254 ms

hm.js

hm.js

2549 ms

2.png

2.png

1767 ms

collect

collect

576 ms

js-sdk-event.min.js

js-sdk-event.min.js

11 ms

3.png

3.png

1670 ms

4.png

4.png

1656 ms

5b.png

5b.png

1664 ms

wx.jpg

wx.jpg

1755 ms

552190.js

552190.js

652 ms

kfm.jpg

kfm.jpg

1661 ms

beian.png

beian.png

1696 ms

line.jpg

line.jpg

1653 ms

slider-arrow.png

slider-arrow.png

1743 ms

altb.jpg

altb.jpg

1660 ms

q1.png

q1.png

1664 ms

q2.png

q2.png

1642 ms

q3.png

q3.png

1643 ms

q4.png

q4.png

1606 ms

s.gif

s.gif

440 ms

mediav1130.html

mediav1130.html

868 ms

proxy.html

proxy.html

436 ms

local.info.g9hc4.cn

local.info.g9hc4.cn

232 ms

s.gif

s.gif

438 ms

local.info.g9hc4.cn

local.info.g9hc4.cn

2 ms

b

b

859 ms

UrlChangeTracker.js

UrlChangeTracker.js

1527 ms

b.js

b.js

2169 ms

hm.gif

hm.gif

324 ms

b.js

b.js

1859 ms

hm.gif

hm.gif

330 ms

pixel

pixel

26 ms

t.gif

t.gif

1287 ms

ckmap.htm

ckmap.htm

981 ms

cm.gif

cm.gif

1406 ms

max.dmp.360.cn

max.dmp.360.cn

1124 ms

pixel

pixel

13 ms

m

m

842 ms

m

m

208 ms

m

m

283 ms

m

m

333 ms

m

m

415 ms

m

m

530 ms

affim.js

affim.js

1987 ms

s.gif

s.gif

428 ms

Accessibility Review

winic.org accessibility score

51

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.

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

winic.org 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

SEO Factors

winic.org SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Winic.org 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 Winic.org 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

winic.org

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