10.7 sec in total
654 ms
9.5 sec
586 ms
Click here to check amazing Geek Park content for China. Otherwise, check out these important facts you probably never knew about geekpark.net
极客公园聚焦互联网领域,跟踪新鲜的科技新闻动态,关注极具创新精神的科技产品。
Visit geekpark.netWe analyzed Geekpark.net page load time and found that the first response time was 654 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
geekpark.net performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value10.0 s
0/100
25%
Value26.2 s
0/100
10%
Value410 ms
67/100
30%
Value0.449
20/100
15%
Value15.4 s
7/100
10%
654 ms
851 ms
1536 ms
2067 ms
2314 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 15% of them (8 requests) were addressed to the original Geekpark.net, 64% (35 requests) were made to Imgslim.geekpark.net and 9% (5 requests) were made to Mainssl.geekpark.net. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Imgslim.geekpark.net.
Page size can be reduced by 236.0 kB (10%)
2.3 MB
2.1 MB
In fact, the total size of Geekpark.net main page is 2.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. 45% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 61.8 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 61.8 kB or 84% of the original size.
Potential reduce by 164.7 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. Geek Park images are well optimized though.
Potential reduce by 9.5 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.
Number of requests can be reduced by 9 (18%)
50
41
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geek Park. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
geekpark.net
654 ms
geekpark.net
851 ms
www.geekpark.net
1536 ms
polyfill.min.js
2067 ms
autotrack-41efffe793b9098b5e4d45ad2c767b1e.js
2314 ms
js
70 ms
common.fbd9b59140021cfd00a8.css
213 ms
common.ab431e4e8e36086362dc.css
463 ms
manifest.599a09bb6d8df7f1fad4.js
614 ms
vendor.ab431e4e8e36086362dc.js
1486 ms
app.fbd9b59140021cfd00a8.js
836 ms
jweixin-1.6.0.js
1117 ms
jquery.min.js
2594 ms
hotkeys.js
2695 ms
linkedme.min.js
2753 ms
copyright.png
620 ms
d63ced73b8ba3abee08981ab59fea5fd.jpeg
858 ms
001d731302c14dd71441659b0ff93be9.jpg
813 ms
b79b317bf7d03a7715e8953221f50052.jpeg
1259 ms
739c6661cf8ca8c3a14c92b7f4bf6a5f.png
1664 ms
077396726f3c342796a9a183c640ed17.png
2058 ms
loading.svg
859 ms
qr_geekpark.jpg
1182 ms
qr_geekchoice.jpg
1246 ms
e597a45ff3ca357331c09863fd6207c1.jpg
1218 ms
qiniu_1.png
1403 ms
qingyun.png
1484 ms
huode_scene_3.png
1537 ms
qr_app.gif
1504 ms
mSNgswAA
3 ms
971be2ecd0a1fd743c55e1cf811dc128.png
1578 ms
2.png
1166 ms
4.png
1385 ms
176C5A76-1DB6-40A8-98AF-EE75C8214E5F_1_201_a.jpeg
1600 ms
8c4d9ccf31cbfc12310faeeb49b025ec.jpg
785 ms
58482109d7c7908c749369d3a4e9105d.png
1028 ms
15149e286abffb40b8e88987d625a5a0.jpg
781 ms
recommendation
222 ms
ads
775 ms
hot_in_week
293 ms
2
517 ms
topics
280 ms
e33c26463d19dfc2a57e34d90ba5431e.png
699 ms
bb73a2822ef1e46531d411d81e6f42ae.jpg
794 ms
077396726f3c342796a9a183c640ed17.png
965 ms
0a4cfddd4334e4a211c37aa26db29023.jpg
227 ms
9868f23bf94c85c088c9f928800fc3a6.jpg
260 ms
202ff0492a5a1a0328c6ada7ea0b2381.jpg
956 ms
739c6661cf8ca8c3a14c92b7f4bf6a5f.png
878 ms
633cc8f243c4d9c3ea2a1223060a1a70.jpg
293 ms
a8643823755cbe1a114f9c3124b4daf6.png
1043 ms
feb115bdd0bfb2317d84b41cbba20254.jpg
700 ms
424e8c0f713942d90589f85fb258dbc8.jpg
818 ms
4889cedd3048ac48d96135f6c0c2085a.png
1960 ms
access_key
217 ms
geekpark.net accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<html> element does not have a [lang] attribute
geekpark.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
geekpark.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geekpark.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 Geekpark.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.
geekpark.net
Open Graph description is not detected on the main page of Geek Park. 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: