Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 39

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

yggk.net

阳光学习网

Page Load Speed

92 sec in total

First Response

12.1 sec

Resources Loaded

78.4 sec

Page Rendered

1.4 sec

yggk.net screenshot

About Website

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

阳光学习网免费分享高考报名、高考招生计划、高考分数线、高考成绩查询、高考志愿填报、高考录取查询、做最专业的学习经验交流学习网.

Visit yggk.net

Key Findings

We analyzed Yggk.net page load time and found that the first response time was 12.1 sec and then it took 79.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. Unfortunately, there were 8 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

yggk.net performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

yggk.net

12134 ms

index.css

1551 ms

jQuery_latest.min.js

4760 ms

jQuery_tabs.js

1741 ms

jQuery_picFocus.js

1738 ms

Our browser made a total of 143 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Yggk.net, 13% (19 requests) were made to Img.yggk.net and 11% (16 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source T11.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 965.0 kB (43%)

Content Size

2.2 MB

After Optimization

1.3 MB

In fact, the total size of Yggk.net main page is 2.2 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. 50% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 140.2 kB

  • Original 165.3 kB
  • After minification 162.7 kB
  • After compression 25.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 140.2 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 15.9 kB

  • Original 787.5 kB
  • After minification 771.6 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. Yggk images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 796.6 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 480.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 796.6 kB or 62% of the original size.

CSS Optimization

-70%

Potential reduce by 12.4 kB

  • Original 17.7 kB
  • After minification 17.7 kB
  • After compression 5.3 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. Yggk.net needs all CSS files to be minified and compressed as it can save up to 12.4 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (53%)

Requests Now

128

After Optimization

60

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

Accessibility Review

yggk.net accessibility score

39

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

yggk.net best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

yggk.net SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yggk.net 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 Yggk.net main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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