7.7 sec in total
1.8 sec
5.3 sec
593 ms
Click here to check amazing Trass Osablog content for Japan. Otherwise, check out these important facts you probably never knew about trass-osablog.com
ウェブ解析士の小佐野宇志(オサノタカシ/株式会社トラス)が日本・海外(中国など)のITについてコラムを書いていきます。エンタメ系のニュースが好きなので、たまに遊びを交えた記事も書いていこうと思います。
Visit trass-osablog.comWe analyzed Trass-osablog.com page load time and found that the first response time was 1.8 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
trass-osablog.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.1 s
76/100
25%
Value7.0 s
32/100
10%
Value260 ms
83/100
30%
Value0
100/100
15%
Value11.5 s
18/100
10%
1849 ms
388 ms
1089 ms
440 ms
442 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 26% of them (33 requests) were addressed to the original Trass-osablog.com, 27% (34 requests) were made to B.hatena.ne.jp and 16% (20 requests) were made to Graph.facebook.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Trass-osablog.com.
Page size can be reduced by 329.7 kB (16%)
2.1 MB
1.8 MB
In fact, the total size of Trass-osablog.com main page is 2.1 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 73.6 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 73.6 kB or 83% of the original size.
Potential reduce by 131.2 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. Trass Osablog images are well optimized though.
Potential reduce by 46.1 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 46.1 kB or 24% of the original size.
Potential reduce by 78.8 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. Trass-osablog.com needs all CSS files to be minified and compressed as it can save up to 78.8 kB or 78% of the original size.
Number of requests can be reduced by 64 (70%)
92
28
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trass Osablog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and as a result speed up the page load time.
trass-osablog.com
1849 ms
wp-emoji-release.min.js
388 ms
style.css
1089 ms
visual-custom.css
440 ms
screen.min.css
442 ms
jquery.min.js
31 ms
adsbygoogle.js
120 ms
widget.js
5 ms
widget.js
15 ms
jquery.easing.min.js
195 ms
imagesloaded.min.js
207 ms
jquery.fitvids.min.js
287 ms
jquery.masonry.min.js
509 ms
theme-import.min.js
387 ms
front.min.js
400 ms
wp-embed.min.js
440 ms
ga.js
67 ms
55 ms
br_c_1000_2.gif
663 ms
56 ms
57 ms
56 ms
60 ms
60 ms
60 ms
60 ms
61 ms
61 ms
%E4%B8%AD%E5%9B%BDIT%E3%83%96%E3%83%AD%E3%82%B0.jpg
628 ms
%E7%99%BE%E5%BA%A6%E9%9B%B2_%E3%83%88%E3%83%83%E3%83%9703.png
1321 ms
%E3%83%88%E3%83%A9%E3%82%B93.png
1308 ms
img_ogp_1200_630.jpg
865 ms
%E5%90%8D%E7%A7%B0%E6%9C%AA%E8%A8%AD%E5%AE%9A-1.jpg
677 ms
%E4%B9%97%E3%81%A3%E5%8F%96%E3%82%8A.jpg
882 ms
143.jpg
847 ms
%E6%97%A5%E6%9C%AC%E3%81%8B%E3%82%89%E4%B8%AD%E5%9B%BD.jpg
1119 ms
001_2.jpg
1618 ms
%E3%83%AD%E3%82%B4.jpg
1059 ms
450.jpg
1102 ms
WAC21213642-avat.jpg
1253 ms
facebook.jpg
1323 ms
%E5%BE%AE%E5%8D%9A.jpg
1338 ms
QQ.jpg
1445 ms
%E5%BE%AE%E4%BF%A1.jpg
1524 ms
mzl.amvyqtlq.png
1758 ms
94c1f677-57bf-422d-b63e-49e89d0ee05a.png
1796 ms
dpicons.svg
2162 ms
dpicons.woff
1580 ms
__utm.gif
57 ms
loading3.gif
1529 ms
favicon.gif
386 ms
widgets.js
54 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D795
94 ms
entry.count
780 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D744
148 ms
entry.count
824 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D701
170 ms
entry.count
830 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D664
170 ms
entry.count
562 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D596
144 ms
entry.count
979 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D564
169 ms
entry.count
1008 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D529
166 ms
entry.count
1040 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D481
171 ms
entry.count
1216 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D456
168 ms
entry.count
1284 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D450
176 ms
entry.count
1256 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D795
168 ms
entry.count
1451 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D369
175 ms
entry.count
1456 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D366
177 ms
entry.count
1468 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D456
210 ms
entry.count
1659 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D481
188 ms
entry.count
1701 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D795
191 ms
entry.count
1750 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D369
214 ms
entry.count
1916 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D366
198 ms
entry.count
1878 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D456
212 ms
entry.count
1911 ms
http%3A%2F%2Ftrass-osablog.com%2F%3Fp%3D481
216 ms
entry.count
2113 ms
json
1906 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
59 ms
00001.gif
58 ms
00012.gif
78 ms
settings
74 ms
00012.gif
12 ms
00002.gif
4 ms
00005.gif
4 ms
00001.gif
20 ms
00008.gif
30 ms
00000.gif
3 ms
00003.gif
5 ms
entry
198 ms
00002.gif
4 ms
entry
151 ms
entry
517 ms
entry
480 ms
entry
476 ms
entry
481 ms
entry
159 ms
entry
154 ms
entry
445 ms
entry
460 ms
entry
478 ms
entry
159 ms
entry
451 ms
entry
156 ms
entry
153 ms
entry
481 ms
entry
452 ms
entry
156 ms
entry
432 ms
entry
166 ms
trass-osablog.com 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
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.
trass-osablog.com 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
Page has valid source maps
trass-osablog.com SEO score
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
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trass-osablog.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Trass-osablog.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.
trass-osablog.com
Open Graph description is not detected on the main page of Trass Osablog. 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: