15.4 sec in total
654 ms
12.7 sec
2 sec
Click here to check amazing I Ra content for Japan. Otherwise, check out these important facts you probably never knew about i-ra.jp
「イーラ・パーク」は、静岡県東部・伊豆エリアの地域ブログポータルサイトです。ブログ作成は無料。ビジネスで活用するブロガーも多数。ブロガー同士のリアルな繋がりが多いブログコミュニティサイトです。釣り/河津桜/日記/ラブライブ/ランチ…
Visit i-ra.jpWe analyzed I-ra.jp page load time and found that the first response time was 654 ms and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
i-ra.jp performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value11.8 s
0/100
25%
Value18.3 s
0/100
10%
Value6,610 ms
0/100
30%
Value0
100/100
15%
Value25.9 s
0/100
10%
654 ms
1405 ms
659 ms
890 ms
687 ms
Our browser made a total of 207 requests to load all elements on the main page. We found that 44% of them (92 requests) were addressed to the original I-ra.jp, 23% (47 requests) were made to Img01.i-ra.jp and 6% (12 requests) were made to Ad.adlantis.jp. The less responsive or slowest element that took the longest time to load (5.6 sec) relates to the external source Img01.i-ra.jp.
Page size can be reduced by 293.2 kB (13%)
2.3 MB
2.0 MB
In fact, the total size of I-ra.jp main page is 2.3 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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 73.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. This page needs HTML code to be minified as it can gain 11.4 kB, which is 12% 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 73.3 kB or 77% of the original size.
Potential reduce by 10.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. I Ra images are well optimized though.
Potential reduce by 175.7 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 175.7 kB or 52% of the original size.
Potential reduce by 34.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. I-ra.jp needs all CSS files to be minified and compressed as it can save up to 34.0 kB or 87% of the original size.
Number of requests can be reduced by 84 (42%)
198
114
The browser has sent 198 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Ra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
i-ra.jp
654 ms
www.i-ra.jp
1405 ms
design.css
659 ms
box_index.css
890 ms
top_rss_list.css
687 ms
pgscroll.js
691 ms
hide.js
687 ms
prototype.js
1582 ms
tabMaker.js
1146 ms
AdLantisLoader.js
1259 ms
jquery1-3.js
1598 ms
jquery.cycle.js
1381 ms
adslide.js
1200 ms
adclick.js
1348 ms
common_str.js
1616 ms
rss_reader.php
2232 ms
adslide_bnr.js
1806 ms
rss_reader.php
2632 ms
show_ads.js
44 ms
brand
20 ms
tabMaker.css
2025 ms
rss_reader.php
2269 ms
brand
129 ms
adsbygoogle.js
25 ms
index.js
357 ms
notfound
2117 ms
analytics.js
135 ms
image548338-s.jpeg
1244 ms
P2160910-s.jpg
1225 ms
bnr200_80fr.gif
1198 ms
bg_body.gif
280 ms
bg_header.gif
1166 ms
bg_entry.jpg
1200 ms
bt_entry.gif
1191 ms
bt_login.gif
1165 ms
bt_menu.gif
1219 ms
pan_icon.gif
1179 ms
bg_news.gif
1199 ms
ico_picture.gif
1219 ms
no1.gif
1222 ms
no2.gif
1543 ms
no3.gif
1606 ms
no4.gif
1614 ms
no5.gif
1609 ms
no6.gif
1772 ms
no7.gif
1753 ms
no8.gif
1911 ms
no9.gif
2067 ms
no10.gif
2067 ms
no11.gif
2068 ms
no12.gif
2265 ms
no13.gif
2279 ms
no14.gif
2361 ms
no15.gif
2600 ms
no16.gif
2600 ms
no17.gif
2600 ms
no18.gif
2901 ms
no19.gif
2901 ms
no20.gif
2976 ms
no21.gif
2990 ms
no22.gif
2990 ms
no23.gif
2976 ms
no24.gif
3186 ms
no25.gif
3186 ms
side.gif
3267 ms
app-053976500s1455587691-s.jpg
1567 ms
app-061732800s1455526068-s.jpg
1749 ms
app-028196500s1455587649-s.jpg
1773 ms
CIMG2154-s.JPG
1161 ms
IMG_2338_2-s.jpg
1161 ms
AutumnsLeaves_1-s.jpg
1973 ms
image_46-s.jpeg
1771 ms
%E3%82%B3%E3%83%94%E3%83%BC%EF%BD%9Es20160216_063914-s.jpg
1571 ms
IMG00042-s.jpg
2518 ms
DSC_0001sk1280x960k_7-s.jpg
2254 ms
%E6%A1%9C%E3%83%AD%E3%83%BC%E3%83%AB-s.gif
2883 ms
%E3%83%AC%E3%83%90%E3%82%B3%E3%83%BC%E3%83%ABs%E5%B1%95%E7%A4%BA-s.jpg
2899 ms
IMG_0324-s.JPG
2514 ms
20160215-s.jpg
2321 ms
%E9%A0%9A%EF%BC%91_1-s.jpg
2853 ms
app-073672500s1455580728-s.jpg
3530 ms
sp-039476900s1455434403-s.jpg
3554 ms
IMG_1469_3-s.jpg
3325 ms
sp-058203400s1455535298-s.jpg
3324 ms
app-053136400s1455581650-s.jpg
3553 ms
sp-031851600s1441007568-s.jpg
3324 ms
CIMG4459-s.JPG
3790 ms
2665_1-s.JPG
4028 ms
003_38-s.JPG
4057 ms
sp-090426700s1455579897-s.jpg
3999 ms
P1040145-s.JPG
4235 ms
app-063509400s1455316050-s.jpg
4938 ms
P1080416-s.jpg
4707 ms
menu-icon.jpg
3425 ms
collect
33 ms
im_li1_04.gif
3223 ms
DSC_7147-s.jpg
4478 ms
%E5%86%99%E7%9C%9Fs2016-02-15s10s52s14-s.jpg
4501 ms
DSC_7151-s.jpg
4501 ms
DSC_7103-s.jpg
4664 ms
njkcamera123-s.JPG
5294 ms
sakura26-s.JPG
4852 ms
916-s.jpg
5582 ms
ajs.php
210 ms
lg.php
23 ms
show_ads_impl.js
124 ms
zrt_lookup.html
73 ms
match.aspx
44 ms
ads
465 ms
im_li1_03.gif
2330 ms
im_li1_05.gif
2463 ms
im_li1_06.gif
2461 ms
ico_point.gif
2578 ms
DSC_6812-s.jpg
4090 ms
DSC_6840-s.jpg
4476 ms
app-028938200s1454749753-s.jpg
4727 ms
c17.gif
2720 ms
im_li1_02.gif
2723 ms
im_li1_07.gif
2712 ms
im_li1.gif
2880 ms
osd.js
283 ms
bnr_fbiz.jpg
3280 ms
ads
273 ms
10129480179985084978
226 ms
abg.js
217 ms
m_js_controller.js
248 ms
googlelogo_color_112x36dp.png
321 ms
type_birthday.gif
2630 ms
1454455425264-s.jpg
4045 ms
CIMG8030-s.JPG
4578 ms
obj_03.gif
2764 ms
bnr_babymam.gif
3218 ms
google_custom_search_watermark.gif
289 ms
bg_body_pink.gif
2623 ms
ajs.php
310 ms
bnr_seminar20160324_468x150.jpg
4001 ms
bnr_mamarazzi_468x150.jpg
3578 ms
app-000247200s1454281168-s.jpg
4741 ms
app-013864000s1454198272-s.jpg
4745 ms
DSCF6677-s.JPG
4573 ms
x_button_blue2.png
94 ms
s
104 ms
favicon
144 ms
s
55 ms
nessie_icon_tiamat_white.png
23 ms
bnr_shizutabi_468x150.jpg
4115 ms
321-s.JPG
4727 ms
-Wxc5n6ag8mSVPmrosQZJ6hEHpQooK3Qr1Gxv0lUkvE.js
7 ms
lg.php
63 ms
match.aspx
66 ms
paging_bg2.png
2839 ms
center_title1.jpg
3141 ms
no_image.jpg
3354 ms
ca-pub-5557325793819817.js
117 ms
ads
345 ms
app-055527300s1454311581-s.jpg
4633 ms
top_blogicon.png
3004 ms
bg_dot.gif
3305 ms
aim_icon.gif
3378 ms
ads
429 ms
mainpic-s.jpg
4673 ms
left_title2.jpg
3657 ms
bg_serch.gif
3337 ms
ads
189 ms
aim_subtitle.gif
3211 ms
left_title1.jpg
3302 ms
aim_green.gif
3296 ms
right_title1.jpg
3431 ms
jump_triangle.gif
3506 ms
bg_areat.gif
3809 ms
adj
250 ms
bg_areab.gif
3533 ms
beacon
202 ms
uh.js
609 ms
444 ms
adlantis.www.js
234 ms
swfobject.js
407 ms
aim_li3.gif
3479 ms
pixel
79 ms
lidar.js
15 ms
sbhK2lTE.js
14 ms
cTrvNaRi.html
23 ms
pixel
72 ms
pixel
67 ms
load_script
473 ms
load_script
471 ms
load_script
387 ms
load_script
472 ms
load_script
473 ms
load_script
472 ms
load_script
733 ms
load_script
743 ms
load_iframe
279 ms
8802e06ddab2a1e044372f338857fcc425d1f0f4.jpg
1411 ms
load_iframe
262 ms
load_iframe
306 ms
load_iframe
374 ms
promenade.png
3080 ms
rss_reader.php
741 ms
leaders_supermedical_148_60.jpg
2963 ms
bgt
830 ms
0.gif
848 ms
ads
246 ms
11477708674420782039
97 ms
s
70 ms
tabmbg.gif
466 ms
ui
213 ms
i-ra.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
i-ra.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
Browser errors were logged to the console
i-ra.jp SEO score
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-ra.jp 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 I-ra.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.
i-ra.jp
Open Graph description is not detected on the main page of I Ra. 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: