4.7 sec in total
318 ms
4.2 sec
174 ms
Visit pigg.ameba.jp now to see the best up-to-date Pigg Ameba content for Japan and also check out these interesting facts you probably never knew about pigg.ameba.jp
2019年12月2日をもちまして、PC版アメーバピグ及びPCピグサービスはサービスを終了いたしました。10年間に及ぶ長らくのご愛顧、誠にありがとうございました。
Visit pigg.ameba.jpWe analyzed Pigg.ameba.jp page load time and found that the first response time was 318 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pigg.ameba.jp performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value11.7 s
0/100
25%
Value4.4 s
74/100
10%
Value10 ms
100/100
30%
Value0.244
51/100
15%
Value6.8 s
55/100
10%
318 ms
805 ms
671 ms
750 ms
747 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Pigg.ameba.jp, 45% (50 requests) were made to Pbs.twimg.com and 35% (38 requests) were made to Ssl.ameba.jp. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Ssl.ameba.jp.
Page size can be reduced by 201.2 kB (15%)
1.4 MB
1.2 MB
In fact, the total size of Pigg.ameba.jp main page is 1.4 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 13.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 13.6 kB or 71% of the original size.
Potential reduce by 66.4 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. Pigg Ameba images are well optimized though.
Potential reduce by 94.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 94.3 kB or 60% of the original size.
Potential reduce by 26.9 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. Pigg.ameba.jp needs all CSS files to be minified and compressed as it can save up to 26.9 kB or 80% of the original size.
Number of requests can be reduced by 26 (25%)
105
79
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pigg Ameba. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
pigg.ameba.jp
318 ms
pigg.ameba.jp
805 ms
i_orgn_160216.css
671 ms
common.hf.white.css
750 ms
swfobject.js
747 ms
jquery-1.7.2.min.js
788 ms
slideshow2.js
800 ms
common.hf.js
633 ms
s.js
870 ms
653 ms
analytics_pigg.js
727 ms
ga.js
62 ms
common.css
327 ms
amebabar_static.css
314 ms
orgn_160216.css
350 ms
img_coordination04.gif
269 ms
img_coordination06.gif
715 ms
img_coordination05.gif
715 ms
img_goout02.gif
267 ms
img_cominucation02.gif
219 ms
fishing.png
266 ms
casino.png
447 ms
daifugo.png
579 ms
mahjong.png
484 ms
bg_160216.png
713 ms
bg_loginBox_150203.png
713 ms
btn_regist05.png
713 ms
btn_start03.png
738 ms
bg_about_in.gif
919 ms
h4_coordination03.gif
955 ms
bg_coordination02.png
964 ms
btn_sl02.png
933 ms
h4_goout03.gif
934 ms
h4_cominucation03.gif
987 ms
game_bg.png
1148 ms
game_title.png
1177 ms
tweet_bg.png
1166 ms
tweet_title.png
1205 ms
widgets.js
123 ms
bg_startbox_150203.png
1178 ms
btn_piggnews_npcRenewal_150819.png
1250 ms
commonHeader.jsonp
1645 ms
abema_bg_logo.png
1708 ms
abema_bg_common_hf.png
1775 ms
604 ms
bl_track.cgi
757 ms
__utm.gif
52 ms
blade_track_jp.js
910 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
28 ms
syndication
97 ms
444366752084803584
434 ms
444366997984268288
233 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
28 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
118 ms
SGNU2uxw_normal.png
255 ms
4FVT3o9I_normal.jpg
247 ms
3B51uIfq_normal.jpg
312 ms
Cb94FcIW0AArgpc.png:small
388 ms
Cb3zVYQUMAA_wbp.jpg:small
310 ms
CbVC8VjUcAAj_LO.png:small
385 ms
CbATteAUEAAC3Ud.jpg:small
309 ms
CarRMChVAAA1KZ3.jpg:small
308 ms
CabhG_8VIAEbfq0.jpg:small
351 ms
CaIAy2FUsAQAm0q.jpg:small
353 ms
CaGv5qcUYAE8mxv.jpg:small
351 ms
CZfnVOwVAAAYDPq.jpg:small
351 ms
CZy5lWQUsAEpEvM.jpg:small
355 ms
CZT7vqIW0AIRCIl.jpg:small
356 ms
CZJ6kMQUAAI_Nui.jpg:small
357 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
40 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
38 ms
default_profile_2_normal.png
102 ms
aZSjFZ8x_normal.jpg
106 ms
nxNuvpH8_normal.jpg
171 ms
nH63DW2g_normal.jpg
128 ms
XB3BvFcF_normal.jpg
129 ms
xmUXlHUw_normal.jpg
129 ms
drk5Wayk_normal.jpeg
130 ms
p8vssjdw_normal.jpeg
141 ms
image_normal
138 ms
BmfoBS6X_normal.jpeg
139 ms
hmA-TgpU_normal.jpg
153 ms
G_pBMKP5_normal.png
151 ms
Jjs66VjH_normal.jpeg
165 ms
YXHVQZ1s_normal.jpeg
167 ms
0V_BFXrV_normal.jpg
169 ms
j0tBvGV6_normal.jpg
178 ms
rh-v7nI5_normal.jpg
178 ms
CcacyBUUcAAKtwE.jpg:small
288 ms
CcacfXhUsAAZi4C.jpg:small
222 ms
CcacCbJVAAAuNly.jpg:small
219 ms
CcabdVlUAAAJ_tP.jpg:small
226 ms
CcabPsUUUAAtrnx.jpg:small
228 ms
CcaabQFUEAAqZW3.jpg:small
281 ms
CcaY4EJUcAAHEwQ.jpg:small
281 ms
CcaYbb8UcAAX1HV.jpg:small
266 ms
CcaYXsKUkAAUtt9.jpg:small
274 ms
CcaXrTsVAAAurPX.jpg:small
212 ms
CcaW3gyUUAAHiVK.jpg:small
226 ms
CcaVrVXVAAA0s2s.jpg:small
221 ms
CcaVdUnUYAEdGtd.jpg:small
219 ms
CcaVQcpUsAAw-KA.jpg:small
252 ms
CcaU2y9UcAAdUKu.jpg:small
227 ms
CcaUKUeUYAAaWjD.jpg:small
246 ms
CcaTz6bUcAAZ-a7.jpg:small
242 ms
CcaTfdPUEAA6vUi.jpg:small
242 ms
CcaShmaVAAA-C8E.jpg:small
243 ms
cookie_enabled_get.html
690 ms
jot.html
33 ms
bl_track.cgi
533 ms
pigg.ameba.jp accessibility score
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
Image elements do not have [alt] attributes
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.
pigg.ameba.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
pigg.ameba.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 doesn't use legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pigg.ameba.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 Pigg.ameba.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.
pigg.ameba.jp
Open Graph data is detected on the main page of Pigg Ameba. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: