10.6 sec in total
3.3 sec
6.8 sec
446 ms
Visit poptie.jp now to see the best up-to-date POPTIE content for Japan and also check out these interesting facts you probably never knew about poptie.jp
Visit poptie.jpWe analyzed Poptie.jp page load time and found that the first response time was 3.3 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
poptie.jp performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value5.0 s
27/100
25%
Value10.0 s
9/100
10%
Value2,210 ms
6/100
30%
Value0
100/100
15%
Value13.8 s
10/100
10%
3334 ms
361 ms
356 ms
56 ms
338 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Poptie.jp, 29% (33 requests) were made to Img.poptie.jp and 13% (15 requests) were made to Cdn.poptie.jp. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Poptie.jp.
Page size can be reduced by 202.6 kB (23%)
865.1 kB
662.5 kB
In fact, the total size of Poptie.jp main page is 865.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 552.7 kB which makes up the majority of the site volume.
Potential reduce by 32.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 32.7 kB or 76% of the original size.
Potential reduce by 35.6 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. POPTIE images are well optimized though.
Potential reduce by 110.9 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 110.9 kB or 46% of the original size.
Potential reduce by 23.4 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. Poptie.jp needs all CSS files to be minified and compressed as it can save up to 23.4 kB or 80% of the original size.
Number of requests can be reduced by 45 (41%)
110
65
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of POPTIE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
poptie.jp
3334 ms
basic.css
361 ms
matome_list.css
356 ms
home.css
56 ms
jquery.sidr.dark.css
338 ms
adsbygoogle.js
20 ms
jquery-1.8.3.min.js
354 ms
jquery.sidr.min.js
21 ms
lib_basic_min.js
25 ms
basic.js
190 ms
analytics.js
33 ms
img
2249 ms
img
2117 ms
img
2170 ms
img
2177 ms
img
2191 ms
img
2226 ms
img
2320 ms
img
2370 ms
img
2385 ms
img
2401 ms
img
2622 ms
img
2443 ms
img
2521 ms
img
2570 ms
img
2594 ms
img
2621 ms
img
2643 ms
img
2722 ms
img
2772 ms
img
2800 ms
img
2830 ms
img
2829 ms
img
2843 ms
img
2926 ms
img
2973 ms
img
3012 ms
img
3227 ms
img
3049 ms
img
3047 ms
img
3128 ms
img
3178 ms
img
3220 ms
img
3246 ms
logo.png
387 ms
logo3.png
386 ms
sdk.js
16 ms
header_sprite.png
373 ms
btn_sprite.png
421 ms
shadow_sprite.png
376 ms
ad-caption.gif
126 ms
collect
48 ms
ca-pub-7618537432990152.js
245 ms
zrt_lookup.html
241 ms
show_ads_impl.js
130 ms
326 ms
xd_arbiter.php
107 ms
xd_arbiter.php
411 ms
widgets.js
175 ms
btn_page_top.png
394 ms
icon_sprite.png
169 ms
platform.js
246 ms
ads
312 ms
osd.js
55 ms
ads
290 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
33 ms
page.php
591 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
28 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
65 ms
page
118 ms
postmessageRelay
76 ms
m_js_controller.js
202 ms
abg.js
242 ms
rs=AGLTcCNwBglnRFJRg0mRD_l9WzbpnP29GQ
19 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
31 ms
rs=AGLTcCPJ_Qx0HXwankZ8SJMM-SuxNwIccw
96 ms
googlelogo_color_112x36dp.png
292 ms
13250232331523409936
229 ms
photo.jpg
355 ms
3193398744-postmessagerelay.js
334 ms
rpc:shindig_random.js
182 ms
jot
308 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
290 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
307 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
336 ms
rs=AGLTcCPJ_Qx0HXwankZ8SJMM-SuxNwIccw
55 ms
favicon
268 ms
nessie_icon_tiamat_white.png
100 ms
rs=AGLTcCPJ_Qx0HXwankZ8SJMM-SuxNwIccw
89 ms
x_button_blue2.png
113 ms
s
65 ms
cv4ERr8UMUY.css
168 ms
q68gy-v_YMF.js
224 ms
k19Xse48j5I.js
271 ms
ihptErjAmMX.js
271 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
42 ms
cb=gapi.loaded_0
37 ms
11136676_1074157365934042_5953016889042777123_n.png
121 ms
12821540_573085159514928_8745384219543731095_n.jpg
117 ms
12036645_772091402895290_974317872701837917_n.jpg
200 ms
12227823_501206063384390_7135451603600920336_n.jpg
286 ms
1379841_10150004552801901_469209496895221757_n.jpg
95 ms
12647526_1667565583484680_3211964750078419870_n.jpg
97 ms
11036721_123481068017383_7509531408361368699_n.jpg
128 ms
12523083_191131431242065_4134316104878529727_n.jpg
101 ms
10007419_386006438206517_1651362422_n.jpg
116 ms
wL6VQj7Ab77.png
90 ms
s7jcwEQH7Sx.png
91 ms
R9a_DtVRZgv.js
6 ms
cUDgRFxaoIk.js
8 ms
0JBr1QHp8Gi.js
5 ms
kDOzhTr2W91.js
7 ms
activeview
13 ms
activeview
13 ms
poptie.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
Links do not have a discernible name
poptie.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
Issues were logged in the Issues panel in Chrome Devtools
poptie.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Poptie.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 Poptie.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.
poptie.jp
Open Graph description is not detected on the main page of POPTIE. 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: