6.7 sec in total
1.3 sec
5.2 sec
192 ms
Click here to check amazing Es OSDN content for Japan. Otherwise, check out these important facts you probably never knew about es.osdn.jp
OSDN es un servicio libre de cargos para los desarrolladores de software de código abierto. Ofrecemos Git/SVN/Mercurial/Bazaar/repositorio CVS, listas de correo, sistema de tráfico de errores, tablón ...
Visit es.osdn.jpWe analyzed Es.osdn.jp page load time and found that the first response time was 1.3 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
es.osdn.jp performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value3.8 s
55/100
25%
Value3.8 s
84/100
10%
Value140 ms
95/100
30%
Value0.075
95/100
15%
Value4.0 s
87/100
10%
1304 ms
1040 ms
826 ms
828 ms
837 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Es.osdn.jp, 60% (53 requests) were made to Static.osdn.jp and 3% (3 requests) were made to Ads.adjust-net.jp. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Static.osdn.jp.
Page size can be reduced by 437.2 kB (42%)
1.0 MB
608.0 kB
In fact, the total size of Es.osdn.jp main page is 1.0 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. Javascripts take 502.9 kB which makes up the majority of the site volume.
Potential reduce by 110.0 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 110.0 kB or 89% of the original size.
Potential reduce by 24.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. Es OSDN images are well optimized though.
Potential reduce by 302.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 302.6 kB or 60% of the original size.
Number of requests can be reduced by 36 (43%)
83
47
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Es OSDN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
es.osdn.jp
1304 ms
base-ccb8734efd6d470a953520b7383034b6.min.css
1040 ms
sitetop.css
826 ms
slick.css
828 ms
slick-theme.css
837 ms
jquery.min.js
66 ms
jquery-ui.min.js
87 ms
base-6214d85b6fd6777d37505784837617cf.min.js
1158 ms
slick.min.js
837 ms
sitetop.js
983 ms
gpt.js
50 ms
analytics.js
56 ms
OSDN_logo_h24.png
202 ms
inbox_24.png
201 ms
spanner_24.png
200 ms
note_24.png
199 ms
globe_24.png
200 ms
36x36_0.png
199 ms
36x36_0.png
355 ms
36x36_0.png
351 ms
36x36_0.png
356 ms
default-photo.png
359 ms
trimmed96x96_0.png
342 ms
trimmed96x96_0.png
521 ms
trimmed96x96_0.png
492 ms
trimmed96x96_0.png
675 ms
trimmed96x96_0.png
678 ms
trimmed96x96_0.png
681 ms
trimmed96x96_0.png
522 ms
trimmed96x96_0.png
644 ms
trimmed96x96_0.png
683 ms
trimmed96x96_0.png
686 ms
trimmed96x96_0.png
791 ms
trimmed96x96_0.png
839 ms
trimmed96x96_0.png
1012 ms
trimmed96x96_0.png
842 ms
trimmed96x96_0.png
846 ms
trimmed96x96_0.png
849 ms
trimmed96x96_0.png
951 ms
trimmed96x96_0.png
1012 ms
trimmed96x96_0.png
1012 ms
trimmed96x96_0.gif
1018 ms
trimmed96x96_0.png
1018 ms
trimmed96x96_0.gif
1095 ms
trimmed96x96_0.png
1185 ms
trimmed96x96_0.png
1183 ms
misc.png
1177 ms
36x36_0.png
1182 ms
pubads_impl_82.js
154 ms
collect
44 ms
collect
84 ms
fontawesome-webfont.woff
1324 ms
slick.woff
1045 ms
36x36_0.png
1149 ms
36x36_0.gif
1153 ms
36x36_0.png
1157 ms
nav-arrow1.png
1158 ms
ads
351 ms
container.html
47 ms
default-photo.png
24 ms
star-on-16.png
1046 ms
star-off-16.png
1157 ms
star-half-16.png
1162 ms
ajax-loader.gif
1165 ms
ads.js
829 ms
aceUAC.js
98 ms
osd.js
23 ms
dref=https%253A%252F%252Fes.osdn.jp%252F
35 ms
dref=https%253A%252F%252Fes.osdn.jp%252F
20 ms
worldvsacjun11_BX_300x250.jpg
45 ms
adchoicesJP_white.png
46 ms
moatad.js
145 ms
n.js
37 ms
um.ashx
45 ms
cs.ashx
71 ms
pixel
56 ms
Pug
83 ms
beacon.js
24 ms
sd
8 ms
cfcm.ashx
41 ms
tap.php
27 ms
cfcm.ashx
64 ms
mt.ashx
48 ms
imp
165 ms
ads
167 ms
ads
333 ms
300-2501f19ba1b93d02aaed98b1ffd64b9ae7b.jpg
159 ms
pixel
12 ms
mapuser
154 ms
es.osdn.jp 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.
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
Links do not have a discernible name
es.osdn.jp 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
es.osdn.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Es.osdn.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Es.osdn.jp 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.
es.osdn.jp
Open Graph data is detected on the main page of Es OSDN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: