Tools & Wizards About Us
igetget.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

igetget.com

得到App，知识就在得到 | 罗振宇罗辑思维全套免费听

Page Load Speed

4.1 sec in total

First Response

680 ms

Resources Loaded

2.8 sec

Page Rendered

571 ms

igetget.com screenshot

About Website

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

超过3500万用户使用得到App。这里有罗振宇,薛兆丰,武志红,香帅,何帆等100位专家学者的独家课程，也有专业说书人为你解读好书，更有上万本电子书等你任意试读

Visit igetget.com

Key Findings

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

Performance Metrics

igetget.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

igetget.com

680 ms

1368 ms

www.igetget.com

375 ms

styles.31184da4b7f4f5189171.css

189 ms

home.54a8326f64828ef31c42.css

198 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Igetget.com, 58% (22 requests) were made to Piccdn3.umiwi.com and 18% (7 requests) were made to Piccdn2.umiwi.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Igetget.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 435.8 kB (13%)

Content Size

3.3 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 25.3 kB

  • Original 34.6 kB
  • After minification 33.5 kB
  • After compression 9.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 25.3 kB or 73% of the original size.

Image Optimization

-13%

Potential reduce by 410.4 kB

  • Original 3.0 MB
  • After minification 2.6 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. Obviously, Igetget needs image optimization as it can save up to 410.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 32 B

  • Original 237.6 kB
  • After minification 237.6 kB
  • After compression 237.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 56 B

  • Original 5.4 kB
  • After minification 5.4 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. Igetget.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (9%)

Requests Now

35

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

igetget.com

igetget.com

680 ms

1368 ms

www.igetget.com

www.igetget.com

375 ms

styles.31184da4b7f4f5189171.css

styles.31184da4b7f4f5189171.css

189 ms

home.54a8326f64828ef31c42.css

home.54a8326f64828ef31c42.css

198 ms

MTYzODc3NDUwMzcw.png

MTYzODc3NDUwMzcw.png

398 ms

202408080426579137727871.jpeg

202408080426579137727871.jpeg

221 ms

MTYzODc3MzY0Mzk1.png

MTYzODc3MzY0Mzk1.png

406 ms

202407221607257886144951.jpeg

202407221607257886144951.jpeg

230 ms

202408050832059092822482.jpeg

202408050832059092822482.jpeg

232 ms

202405290749386125198746.jpeg

202405290749386125198746.jpeg

233 ms

202402280415303547520719.jpeg

202402280415303547520719.jpeg

235 ms

201912121343005044860898.png

201912121343005044860898.png

233 ms

201912121342120114124585.jpeg

201912121342120114124585.jpeg

230 ms

201912111849091663777303.jpeg

201912111849091663777303.jpeg

236 ms

201912111855114138401561.jpeg

201912111855114138401561.jpeg

237 ms

201912111902310834262312.jpeg

201912111902310834262312.jpeg

236 ms

201912111903556177210316.jpeg

201912111903556177210316.jpeg

337 ms

202106221111323526017709.jpeg

202106221111323526017709.jpeg

338 ms

201909271441083749680026.jpeg

201909271441083749680026.jpeg

339 ms

201909271451208586400388.jpeg

201909271451208586400388.jpeg

338 ms

201909271455257759137815.jpeg

201909271455257759137815.jpeg

339 ms

201909271510006969133665.jpeg

201909271510006969133665.jpeg

339 ms

201909271534079019746220.jpeg

201909271534079019746220.jpeg

340 ms

manifest.9e384554aaaf70553647.js

manifest.9e384554aaaf70553647.js

205 ms

vendor.768d5bee9c36ec304a4c.js

vendor.768d5bee9c36ec304a4c.js

236 ms

styles.bf40b8cadd96d2c21f27.js

styles.bf40b8cadd96d2c21f27.js

212 ms

home.058b1efb5d0fe397113d.js

home.058b1efb5d0fe397113d.js

212 ms

MTYwODYzMTk2Nzg1.png

MTYwODYzMTk2Nzg1.png

410 ms

201909271552314865768602.jpeg

201909271552314865768602.jpeg

339 ms

202106250944415044946741.jpeg

202106250944415044946741.jpeg

339 ms

202406130911001149441306.jpeg

202406130911001149441306.jpeg

340 ms

202106250945003393099389.jpeg

202106250945003393099389.jpeg

341 ms

202106250945107565404175.jpeg

202106250945107565404175.jpeg

341 ms

MTU2OTIyMzY3MjY3.png

MTU2OTIyMzY3MjY3.png

191 ms

MTU3NTM1NDYwNDEw.png

MTU3NTM1NDYwNDEw.png

196 ms

MTU2Mzc3ODcyMTcy.png

MTU2Mzc3ODcyMTcy.png

197 ms

MTU2Nzk5Njg3MjU2.png

MTU2Nzk5Njg3MjU2.png

197 ms

Accessibility Review

igetget.com accessibility score

64

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

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

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

igetget.com SEO score

92

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

    ZH

  • Encoding

    UTF-8

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

igetget.com

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