7.5 sec in total
1.4 sec
5.5 sec
625 ms
Visit page-i.com now to see the best up-to-date Page I content and also check out these interesting facts you probably never knew about page-i.com
iPhone, iPad, Macユーザーの為の、Apple関連情報サイトです。
Visit page-i.comWe analyzed Page-i.com page load time and found that the first response time was 1.4 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
page-i.com performance score
1394 ms
674 ms
1219 ms
534 ms
360 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 51% of them (27 requests) were addressed to the original Page-i.com, 11% (6 requests) were made to Pagead2.googlesyndication.com and 9% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Page-i.com.
Page size can be reduced by 141.1 kB (23%)
607.9 kB
466.8 kB
In fact, the total size of Page-i.com main page is 607.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. 50% of websites need less resources to load. Images take 379.2 kB which makes up the majority of the site volume.
Potential reduce by 33.1 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 5.7 kB, which is 13% 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 33.1 kB or 76% of the original size.
Potential reduce by 9.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. Page I images are well optimized though.
Potential reduce by 81.0 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 81.0 kB or 49% of the original size.
Potential reduce by 17.5 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. Page-i.com needs all CSS files to be minified and compressed as it can save up to 17.5 kB or 81% of the original size.
Number of requests can be reduced by 26 (58%)
45
19
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Page I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.page-i.com
1394 ms
style.css
674 ms
jquery.js
1219 ms
jquery-migrate.min.js
534 ms
external-tracking.min.js
360 ms
wp-chgfontsize.js
556 ms
tmkm-amazon.css
540 ms
wpp.css
691 ms
show_ads.js
4 ms
widgets.js
85 ms
reset.css
170 ms
ga.js
28 ms
feed-icon16x16.png
28 ms
top-bg.gif
180 ms
pagei1.png
179 ms
136887997-480x320.jpg
1231 ms
14iphone-image7-popup-90x59.jpg
524 ms
2360-480x320.jpg
898 ms
136888025-480x320.jpg
349 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2012-01-14-22.15.01-480x299.png
995 ms
infinity-blade-2-68_large_verge_medium_landscape-480x360.jpg
1042 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2012-01-08-13.20.08-640x392.png
1022 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2011-12-17-14.50.33.png
1465 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2011-11-01-3.01.34-480x249.png
1601 ms
1319734542_27023-90x90.png
1500 ms
iPhone3_Tate3.png
2198 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2011-10-31-11.39.58-480x235.png
1895 ms
1319643831_2950-90x90.png
1407 ms
iPhone1_Tate.png
1946 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2011-10-30-11.55.57.png
2414 ms
ca-pub-6248524944489745.js
155 ms
zrt_lookup.html
155 ms
show_ads_impl.js
71 ms
border-bg.gif
2309 ms
bsa.js
102 ms
__utm.gif
102 ms
ads
235 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
121 ms
osd.js
10 ms
s_3ce5ece1065726f457e33e20de205851.js
28 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
45 ms
info.json
134 ms
794 ms
m_js_controller.js
19 ms
abg.js
32 ms
googlelogo_color_112x36dp.png
50 ms
nessie_icon_magazine_black.png
36 ms
nessie_icon_magazine_white.png
44 ms
s
21 ms
x_button_blue2.png
18 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
5 ms
jot
90 ms
activeview
12 ms
page-i.com SEO score
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Page-i.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Page-i.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.
page-i.com
Open Graph description is not detected on the main page of Page I. 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: