Tools & Wizards About Us
willyton.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

willyton.com

问鼎pc入口-（官网）入口v4.2.0

Page Load Speed

43.7 sec in total

First Response

11.9 sec

Resources Loaded

31.6 sec

Page Rendered

204 ms

willyton.com screenshot

About Website

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

欢迎点击问鼎pc入口,选择问鼎pc入口就是因为它这里是可以大家聚在一起玩的,问鼎pc入口提供多种语言,所以我们只会为您提供精品服务；关注您的需求——如关注我们的未来。

Visit willyton.com

Key Findings

We analyzed Willyton.com page load time and found that the first response time was 11.9 sec and then it took 31.8 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.

Performance Metrics

willyton.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

55/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value25.7 s

0/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.822

4/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

willyton.com

11857 ms

system.css

470 ms

system.css

471 ms

sudyNav.css

467 ms

simplenews.css

467 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 18% of them (11 requests) were addressed to the original Willyton.com, 48% (30 requests) were made to Tmu.edu.cn and 21% (13 requests) were made to Hwczx.com. The less responsive or slowest element that took the longest time to load (18.1 sec) relates to the external source Hwczx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.4 kB (2%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-70%

Potential reduce by 3.2 kB

  • Original 4.6 kB
  • After minification 4.6 kB
  • After compression 1.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. 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 3.2 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 15.6 kB

  • Original 1.3 MB
  • After minification 1.3 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. Willyton images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 6.6 kB

  • Original 13.2 kB
  • After minification 13.1 kB
  • After compression 6.6 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 6.6 kB or 50% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

willyton.com

willyton.com

11857 ms

system.css

system.css

470 ms

system.css

system.css

471 ms

sudyNav.css

sudyNav.css

467 ms

simplenews.css

simplenews.css

467 ms

dtjt9.css

dtjt9.css

471 ms

default.css

default.css

510 ms

style.css

style.css

686 ms

js.js

js.js

677 ms

system_editor.css

system_editor.css

232 ms

index.php

index.php

1192 ms

hm.js

hm.js

1285 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

973 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

876 ms

_visitcount

_visitcount

10726 ms

push.js

push.js

817 ms

2022BG.png

2022BG.png

821 ms

main_02.jpg

main_02.jpg

1038 ms

main_01.jpg

main_01.jpg

1252 ms

main_10.jpg

main_10.jpg

1251 ms

left1_01.jpg

left1_01.jpg

1265 ms

main_04.jpg

main_04.jpg

1261 ms

21266713.js

21266713.js

1047 ms

20348599.js

20348599.js

1092 ms

ky-2023-6-1000x100.gif

ky-2023-6-1000x100.gif

854 ms

2023_6_12_leyu_1000x100.gif

2023_6_12_leyu_1000x100.gif

2274 ms

huohu-1000x200-xin-b.gif

huohu-1000x200-xin-b.gif

1452 ms

BVA-446_EO_1000x200.gif

BVA-446_EO_1000x200.gif

2073 ms

bandao2406191000-100.gif

bandao2406191000-100.gif

1455 ms

pingbo-2023-8-1-1000x100.gif

pingbo-2023-8-1-1000x100.gif

1056 ms

211229-NewPlayerAF-1000x100.gif

211229-NewPlayerAF-1000x100.gif

1919 ms

chsbng_1000x100.gif

chsbng_1000x100.gif

3376 ms

William-2023-7-27_1000x100.gif

William-2023-7-27_1000x100.gif

1865 ms

wanbo-1000X200-xin-b.gif

wanbo-1000X200-xin-b.gif

18074 ms

bying-1000x200.gif

bying-1000x200.gif

16647 ms

picture_bigbanner001.jpg

picture_bigbanner001.jpg

2133 ms

hm.gif

hm.gif

311 ms

main_09-11.jpg

main_09-11.jpg

1056 ms

main2_03.gif

main2_03.gif

1071 ms

button3.gif

button3.gif

1250 ms

line1.gif

line1.gif

1248 ms

main_14.jpg

main_14.jpg

1266 ms

button1.gif

button1.gif

1257 ms

main_16.jpg

main_16.jpg

1069 ms

main_19.jpg

main_19.jpg

1092 ms

wp_article_li_1.png

wp_article_li_1.png

1257 ms

2022BG.png

2022BG.png

2557 ms

main_02.jpg

main_02.jpg

941 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

433 ms

main_10.jpg

main_10.jpg

722 ms

main_01.jpg

main_01.jpg

1209 ms

main_04.jpg

main_04.jpg

934 ms

main_09-11.jpg

main_09-11.jpg

942 ms

left1_01.jpg

left1_01.jpg

945 ms

main2_03.gif

main2_03.gif

910 ms

line1.gif

line1.gif

954 ms

button3.gif

button3.gif

961 ms

button1.gif

button1.gif

949 ms

main_14.jpg

main_14.jpg

952 ms

main_16.jpg

main_16.jpg

1169 ms

main_19.jpg

main_19.jpg

1136 ms

wp_article_li_1.png

wp_article_li_1.png

974 ms

Accessibility Review

willyton.com accessibility score

51

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

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

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

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

willyton.com SEO score

85

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

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

willyton.com

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