Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

gter.net

寄托天下_中立的出国留学申请和考试交流平台|留学资讯|DIY留学|留学经验|留学考试|海外生活 寄托天下出国留学网

Page Load Speed

16.2 sec in total

First Response

1 sec

Resources Loaded

14.2 sec

Page Rendered

1 sec

gter.net screenshot

About Website

Welcome to gter.net homepage info - get ready to check Gter best content for China right away, or after learning these important things about gter.net

提供最有用的出国留学资讯和最热心的留学交流论坛。在BBS上,你可以咨询签证, 面试, 机经, offer, 奖学金, 名校专业等, 也可以分享雅思、托福、GRE的学习心得。无论你留学在美国、加拿大、英国还是澳洲, 都能在留学论坛上找到寄托情感的归宿。

Visit gter.net

Key Findings

We analyzed Gter.net page load time and found that the first response time was 1 sec and then it took 15.2 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

gter.net performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

gter.net

1004 ms

swiper.min.css

694 ms

style.css

698 ms

style.css

699 ms

renting.css

699 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Gter.net, 53% (72 requests) were made to App.gter.net and 42% (57 requests) were made to Oss.gter.net. The less responsive or slowest element that took the longest time to load (11.3 sec) relates to the external source Oss.gter.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.3 kB (8%)

Content Size

2.2 MB

After Optimization

2.0 MB

In fact, the total size of Gter.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. 55% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 116.6 kB

  • Original 137.8 kB
  • After minification 88.6 kB
  • After compression 21.3 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 49.2 kB, which is 36% 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 116.6 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 20.3 kB

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

JavaScript Optimization

-16%

Potential reduce by 25.4 kB

  • Original 163.7 kB
  • After minification 163.7 kB
  • After compression 138.3 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 25.4 kB or 16% of the original size.

CSS Optimization

-24%

Potential reduce by 6.0 kB

  • Original 24.6 kB
  • After minification 24.6 kB
  • After compression 18.6 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. Gter.net needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (25%)

Requests Now

109

After Optimization

82

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

Accessibility Review

gter.net accessibility score

54

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.

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

gter.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

gter.net SEO score

85

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gter.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Gter.net 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

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