4.5 sec in total
706 ms
3.7 sec
180 ms
Click here to check amazing Ur BLOG content for Japan. Otherwise, check out these important facts you probably never knew about ur-blog.jp
URBAN RESEARCHのオフィシャルブログです。
Visit ur-blog.jpWe analyzed Ur-blog.jp page load time and found that the first response time was 706 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ur-blog.jp performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value4.1 s
46/100
25%
Value7.4 s
28/100
10%
Value650 ms
46/100
30%
Value0
100/100
15%
Value8.3 s
40/100
10%
706 ms
340 ms
335 ms
345 ms
347 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 97% of them (76 requests) were addressed to the original Ur-blog.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ur-blog.jp.
Page size can be reduced by 80.5 kB (20%)
402.9 kB
322.5 kB
In fact, the total size of Ur-blog.jp main page is 402.9 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. Images take 277.3 kB which makes up the majority of the site volume.
Potential reduce by 12.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 12.6 kB or 79% of the original size.
Potential reduce by 4.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. Ur BLOG images are well optimized though.
Potential reduce by 49.2 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 49.2 kB or 54% of the original size.
Potential reduce by 14.0 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. Ur-blog.jp needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 78% of the original size.
Number of requests can be reduced by 31 (40%)
77
46
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ur BLOG. 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 from 7 to 1 for CSS and as a result speed up the page load time.
ur-blog.jp
706 ms
reset.css
340 ms
layout.css
335 ms
module.css
345 ms
theme.css
347 ms
iTopicPath.css
348 ms
iBannerArea.css
776 ms
components.css
500 ms
jquery-1.4.2.min.js
851 ms
jquery.cookie.js
514 ms
common.js
515 ms
header.gif
173 ms
globalnavi.gif
335 ms
vr.gif
173 ms
title.gif
176 ms
hr.gif
187 ms
subtitle1.gif
175 ms
8_pt.jpg
345 ms
logo_08.gif
345 ms
updatecount.gif
347 ms
linkto_08.gif
350 ms
1_pt.jpg
372 ms
logo_01.gif
503 ms
linkto_01.gif
516 ms
3_pt.jpg
688 ms
logo_03.gif
518 ms
linkto_03.gif
523 ms
2_pt.jpg
557 ms
logo_02.gif
668 ms
linkto_02.gif
689 ms
6_pt.jpg
691 ms
logo_06.gif
696 ms
linkto_06.gif
742 ms
4_pt.jpg
834 ms
logo_04.gif
860 ms
linkto_04.gif
861 ms
27_pt.jpg
1033 ms
logo_27.gif
869 ms
linkto_27.gif
925 ms
31_pt.jpg
1168 ms
logo_31.gif
1031 ms
linkto_31.gif
1031 ms
5_pt.jpg
1216 ms
logo_05.gif
1110 ms
linkto_05.gif
1202 ms
9_pt.jpg
1203 ms
ga.js
30 ms
logo_09.gif
1181 ms
__utm.gif
12 ms
linkto_09.gif
1129 ms
10_pt.jpg
1170 ms
logo_10.gif
1206 ms
linkto_10.gif
1206 ms
22_pt.jpg
1197 ms
logo_22.gif
1063 ms
linkto_22.gif
1142 ms
30_pt.jpg
1166 ms
logo_30.gif
1206 ms
linkto_30.gif
1204 ms
img_staffstyle.jpg
1527 ms
tit_urstyle.png
1069 ms
img_urstyle.jpg
1338 ms
tit_urstyleapp.png
1160 ms
subtitle2.gif
1201 ms
18_pt.jpg
1168 ms
logo_19.gif
1075 ms
linkto_19.gif
1157 ms
25_pt.jpg
1378 ms
logo_25.gif
1210 ms
linkto_25.gif
1222 ms
26_pt.jpg
1272 ms
logo_26.gif
1205 ms
linkto_26.gif
1207 ms
footer.png
1208 ms
h_footer_menu.png
1221 ms
icons.gif
1254 ms
h_footer_brand.png
1194 ms
h_footer_ec.png
1207 ms
ur-blog.jp accessibility score
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
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.
ur-blog.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ur-blog.jp 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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ur-blog.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Ur-blog.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.
ur-blog.jp
Open Graph description is not detected on the main page of Ur BLOG. 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: