53.9 sec in total
2.2 sec
51.1 sec
540 ms
Welcome to static.oschina.net homepage info - get ready to check Static Oschina best content for China right away, or after learning these important things about static.oschina.net
开源中国 www.oschina.net 是目前中国最大的开源技术社区。我们传播开源的理念,推广开源项目,为 IT 开发者提供了一个发现、使用、并交流开源技术的平台。目前开源中国社区已收录超过两万款开源软件。
Visit static.oschina.netWe analyzed Static.oschina.net page load time and found that the first response time was 2.2 sec and then it took 51.6 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 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
static.oschina.net performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value5.8 s
15/100
25%
Value9.5 s
12/100
10%
Value1,540 ms
13/100
30%
Value0
100/100
15%
Value44.8 s
0/100
10%
2245 ms
2903 ms
2905 ms
1549 ms
1820 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that all of those requests were addressed to Static.oschina.net and no external sources were called. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Static.oschina.net.
Page size can be reduced by 666.1 kB (69%)
959.3 kB
293.2 kB
In fact, the total size of Static.oschina.net main page is 959.3 kB. 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. CSS take 383.5 kB which makes up the majority of the site volume.
Potential reduce by 152.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. This page needs HTML code to be minified as it can gain 53.2 kB, which is 30% 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 152.4 kB or 85% of the original size.
Potential reduce by 39.9 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. Obviously, Static Oschina needs image optimization as it can save up to 39.9 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 127.4 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 127.4 kB or 70% of the original size.
Potential reduce by 346.4 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. Static.oschina.net needs all CSS files to be minified and compressed as it can save up to 346.4 kB or 90% of the original size.
Number of requests can be reduced by 22 (34%)
65
43
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Static Oschina. 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 11 to 1 for CSS and as a result speed up the page load time.
static.oschina.net
2245 ms
channel.css
2903 ms
jquery.fancybox-1.3.4.css
2905 ms
nature.css
1549 ms
object.css
1820 ms
people.css
1426 ms
place.css
1921 ms
Sysmbols.css
1933 ms
twemoji.css
2947 ms
jquery-1.7.1.min.js
9364 ms
jquery.form.js
5276 ms
jquery.fancybox-fixed.js
2381 ms
tip-yellowsimple.css
2841 ms
jquery.poshytip.min.js
3304 ms
oschina.js
3346 ms
utils.js
6916 ms
channel.js
3394 ms
oschina2013.css
3763 ms
font-awesome.css
4374 ms
down3.gif
464 ms
logo.svg
1957 ms
newindex-01.svg
464 ms
newindex-02.svg
469 ms
newindex-03.svg
554 ms
icons2.gif
467 ms
index_banner_one_qAQWm.jpg
4200 ms
index_banner_two_xHPVa.jpg
4651 ms
thread_2.gif
1798 ms
thread_1.gif
929 ms
index_banner_three_nWxTV.jpg
13617 ms
index_banner_four_aBYIZ.jpg
3785 ms
index_banner_five_flMjB.jpg
3761 ms
174025_50.jpg
3721 ms
img.gif
6619 ms
2306455_50.jpg
4232 ms
2257615_50.jpg
4246 ms
208591_50.png
6399 ms
2491310_50.jpg
4693 ms
1164691_50.jpg
4710 ms
567557_50.jpg
6454 ms
1756518_50.jpg
5208 ms
1047640_50.jpg
5208 ms
29145950_glho.png
10162 ms
team.png
6961 ms
git.png
8161 ms
sonar.png
6914 ms
paas.png
7650 ms
ostools.gif
7375 ms
runjs_logo.gif
7422 ms
maven.gif
7835 ms
logo.png
7886 ms
111924_i4x6_179699.jpg
9621 ms
160442_8Fw6_179699.png
9751 ms
job_com_ico.png
8250 ms
job_pos_ico.png
8524 ms
fontawesome-webfont.woff
19628 ms
msg.png
8657 ms
people.png
19624 ms
tweetsSwitcher1.gif
9635 ms
tweetsSwitcher2.gif
9670 ms
a3.gif
10349 ms
appIcon.gif
8837 ms
android.gif
8741 ms
iphone.gif
7380 ms
wp7.gif
7411 ms
tweetsSwitcher4.gif
7783 ms
tweetsSwitcher3.gif
7438 ms
gotop.gif
8709 ms
fontawesome-webfont.ttf
19766 ms
static.oschina.net accessibility score
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
static.oschina.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
static.oschina.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
N/A
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Static.oschina.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Chinese. Our system also found out that Static.oschina.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.
static.oschina.net
Open Graph description is not detected on the main page of Static Oschina. 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: