Tools & Wizards About Us
img.ur-blog.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

img.ur-blog.jp

URBAN RESEARCH - Blog Index

Page Load Speed

5.6 sec in total

First Response

730 ms

Resources Loaded

4.7 sec

Page Rendered

173 ms

img.ur-blog.jp screenshot

About Website

Click here to check amazing Img Ur Blog content for Japan. Otherwise, check out these important facts you probably never knew about img.ur-blog.jp

URBAN RESEARCHのオフィシャルブログです。

Visit img.ur-blog.jp

Key Findings

We analyzed Img.ur-blog.jp page load time and found that the first response time was 730 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

img.ur-blog.jp performance score

0

Network Requests Diagram

img.ur-blog.jp

730 ms

reset.css

348 ms

layout.css

355 ms

module.css

359 ms

theme.css

356 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 Img.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 (2 sec) belongs to the original domain Img.ur-blog.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.5 kB (20%)

Content Size

407.6 kB

After Optimization

327.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Img.ur-blog.jp main page is 407.6 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 281.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 12.6 kB

  • Original 15.9 kB
  • After minification 14.8 kB
  • After compression 3.3 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.

Image Optimization

-2%

Potential reduce by 4.7 kB

  • Original 281.9 kB
  • After minification 277.1 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. Img Ur Blog images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 49.2 kB

  • Original 91.8 kB
  • After minification 91.1 kB
  • After compression 42.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 49.2 kB or 54% of the original size.

CSS Optimization

-78%

Potential reduce by 14.0 kB

  • Original 18.0 kB
  • After minification 14.2 kB
  • After compression 4.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. Img.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.

Requests Breakdown

Number of requests can be reduced by 31 (40%)

Requests Now

77

After Optimization

46

  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Img 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.

Network Requests Diagram

img.ur-blog.jp

img.ur-blog.jp

730 ms

reset.css

reset.css

348 ms

layout.css

layout.css

355 ms

module.css

module.css

359 ms

theme.css

theme.css

356 ms

iTopicPath.css

iTopicPath.css

362 ms

iBannerArea.css

iBannerArea.css

421 ms

components.css

components.css

562 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

1052 ms

jquery.cookie.js

jquery.cookie.js

531 ms

common.js

common.js

532 ms

header.gif

header.gif

352 ms

globalnavi.gif

globalnavi.gif

459 ms

vr.gif

vr.gif

324 ms

title.gif

title.gif

341 ms

hr.gif

hr.gif

320 ms

subtitle1.gif

subtitle1.gif

221 ms

8_pt.jpg

8_pt.jpg

542 ms

logo_08.gif

logo_08.gif

556 ms

updatecount.gif

updatecount.gif

604 ms

linkto_08.gif

linkto_08.gif

605 ms

1_pt.jpg

1_pt.jpg

620 ms

logo_01.gif

logo_01.gif

671 ms

linkto_01.gif

linkto_01.gif

780 ms

3_pt.jpg

3_pt.jpg

1077 ms

logo_03.gif

logo_03.gif

894 ms

linkto_03.gif

linkto_03.gif

846 ms

2_pt.jpg

2_pt.jpg

873 ms

logo_02.gif

logo_02.gif

932 ms

linkto_02.gif

linkto_02.gif

997 ms

6_pt.jpg

6_pt.jpg

1045 ms

logo_06.gif

logo_06.gif

1152 ms

linkto_06.gif

linkto_06.gif

1179 ms

4_pt.jpg

4_pt.jpg

1198 ms

logo_04.gif

logo_04.gif

1253 ms

linkto_04.gif

linkto_04.gif

1290 ms

27_pt.jpg

27_pt.jpg

1354 ms

logo_27.gif

logo_27.gif

1416 ms

linkto_27.gif

linkto_27.gif

1389 ms

31_pt.jpg

31_pt.jpg

1455 ms

logo_31.gif

logo_31.gif

1466 ms

linkto_31.gif

linkto_31.gif

1490 ms

5_pt.jpg

5_pt.jpg

1896 ms

logo_05.gif

logo_05.gif

1599 ms

linkto_05.gif

linkto_05.gif

1654 ms

9_pt.jpg

9_pt.jpg

1763 ms

ga.js

ga.js

5 ms

logo_09.gif

logo_09.gif

1667 ms

__utm.gif

__utm.gif

10 ms

linkto_09.gif

linkto_09.gif

1502 ms

10_pt.jpg

10_pt.jpg

1580 ms

logo_10.gif

logo_10.gif

1596 ms

linkto_10.gif

linkto_10.gif

1639 ms

22_pt.jpg

22_pt.jpg

1651 ms

logo_22.gif

logo_22.gif

1518 ms

linkto_22.gif

linkto_22.gif

1553 ms

30_pt.jpg

30_pt.jpg

1566 ms

logo_30.gif

logo_30.gif

1543 ms

linkto_30.gif

linkto_30.gif

1576 ms

img_staffstyle.jpg

img_staffstyle.jpg

1953 ms

tit_urstyle.png

tit_urstyle.png

1650 ms

img_urstyle.jpg

img_urstyle.jpg

1736 ms

tit_urstyleapp.png

tit_urstyleapp.png

1552 ms

subtitle2.gif

subtitle2.gif

1503 ms

18_pt.jpg

18_pt.jpg

1789 ms

logo_19.gif

logo_19.gif

1580 ms

linkto_19.gif

linkto_19.gif

1656 ms

25_pt.jpg

25_pt.jpg

1779 ms

logo_25.gif

logo_25.gif

1627 ms

linkto_25.gif

linkto_25.gif

1556 ms

26_pt.jpg

26_pt.jpg

1597 ms

logo_26.gif

logo_26.gif

1649 ms

linkto_26.gif

linkto_26.gif

1624 ms

footer.png

footer.png

1656 ms

h_footer_menu.png

h_footer_menu.png

1651 ms

icons.gif

icons.gif

1696 ms

h_footer_brand.png

h_footer_brand.png

1663 ms

h_footer_ec.png

h_footer_ec.png

1626 ms

SEO Factors

img.ur-blog.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Img.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 Img.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.

Social Sharing Optimization

img.ur-blog.jp

Open Graph description is not detected on the main page of Img 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: