3.8 sec in total
521 ms
3 sec
291 ms
Visit foodpia.geocities.jp now to see the best up-to-date Foodpia Geocities content for Japan and also check out these interesting facts you probably never knew about foodpia.geocities.jp
400万人以上が利用しているホームページ作成サービス。無料で簡単にホームページを作成できます。独自ドメインや商用利用も可能です。
Visit foodpia.geocities.jpWe analyzed Foodpia.geocities.jp page load time and found that the first response time was 521 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
foodpia.geocities.jp performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value5.0 s
27/100
25%
Value6.3 s
42/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value5.9 s
65/100
10%
521 ms
661 ms
450 ms
446 ms
446 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Foodpia.geocities.jp, 61% (31 requests) were made to I.yimg.jp and 18% (9 requests) were made to Ai.yimg.jp. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source I.yimg.jp.
Page size can be reduced by 229.9 kB (29%)
779.5 kB
549.6 kB
In fact, the total size of Foodpia.geocities.jp main page is 779.5 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 464.4 kB which makes up the majority of the site volume.
Potential reduce by 21.7 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 21.7 kB or 74% of the original size.
Potential reduce by 14.5 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. Foodpia Geocities images are well optimized though.
Potential reduce by 170.3 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 170.3 kB or 66% of the original size.
Potential reduce by 23.3 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. Foodpia.geocities.jp needs all CSS files to be minified and compressed as it can save up to 23.3 kB or 80% of the original size.
Number of requests can be reduced by 14 (29%)
49
35
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foodpia Geocities. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
foodpia.geocities.jp
521 ms
geocities.yahoo.co.jp
661 ms
std.css
450 ms
defaultSettings_01.css
446 ms
style_common_01.css
446 ms
style_guestTop_01.css
450 ms
jquery-1.10.2.min.js
603 ms
ult.js
464 ms
ult.js
451 ms
pcore-1.0.1.min.js
451 ms
yjsecure.js
471 ms
guestTop_01.js
488 ms
rapidjp-1.0.0.js
749 ms
geocities_r_34_2x.png
157 ms
sdk.js
56 ms
std-min.js
169 ms
uftChnk.png
165 ms
top_guest01_bg_mv_01.jpg
619 ms
top_guest01_img_headTxt_01.png
161 ms
top_guest01_img_leadTxt_01.png
168 ms
top_guest01_bg_mv_02.jpg
876 ms
top_guest01_img_headTxt_02.png
161 ms
top_guest01_img_leadTxt_02.png
269 ms
top_guest01_bg_mv_03.jpg
778 ms
top_guest01_img_headTxt_03.png
315 ms
top_guest01_img_leadTxt_03.png
339 ms
top_guest00_icon_info_01.png
419 ms
top_guest00_icon_mystore_01.png
470 ms
top_guest00_bg_planPtn_01.png
666 ms
top_guest00_bg_toPlanArrow_01.png
593 ms
top_guest00_img_planTtl_01.png
628 ms
top_guest00_bg_plusTtl_01.png
736 ms
top_guest00_bg_applyArrowPlus_01.png
778 ms
top_guest00_icon_checkPlus_01.png
785 ms
top_guest00_bg_othersTtl_01.png
1062 ms
top_guest00_bg_applyArrowOther_01.png
896 ms
top_guest00_icon_checkOther_01.png
939 ms
top_guest00_icon_checkNone_01.png
937 ms
common_icon_arrowRightSmall_01.png
937 ms
top_guest00_bg_toBtmBtn_01.png
1057 ms
112 ms
xd_arbiter.php
47 ms
xd_arbiter.php
81 ms
widgets.js
1076 ms
lib2obf_b11.js
159 ms
btn_search_2x.png
160 ms
b
337 ms
xd_arbiter.php
20 ms
share_button.php
105 ms
vpc6VNjRPXV.js
68 ms
LVx-xkvaJ0b.png
38 ms
foodpia.geocities.jp accessibility score
foodpia.geocities.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
foodpia.geocities.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foodpia.geocities.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 Foodpia.geocities.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.
foodpia.geocities.jp
Open Graph data is detected on the main page of Foodpia Geocities. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: