8 sec in total
1.6 sec
5.9 sec
427 ms
Welcome to pop-town.net homepage info - get ready to check Pop Town best content right away, or after learning these important things about pop-town.net
新生オペラパークポップタウン住道がいよいよ誕生。京阪百貨店と100の専門店でJR学研都市線沿線がさらに便利に。
Visit pop-town.netWe analyzed Pop-town.net page load time and found that the first response time was 1.6 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
pop-town.net performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value10.5 s
0/100
25%
Value10.3 s
8/100
10%
Value20 ms
100/100
30%
Value0.531
14/100
15%
Value7.9 s
44/100
10%
1639 ms
705 ms
372 ms
440 ms
457 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 58% of them (66 requests) were addressed to the original Pop-town.net, 31% (35 requests) were made to Pbs.twimg.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Pop-town.net.
Page size can be reduced by 322.1 kB (11%)
2.9 MB
2.6 MB
In fact, the total size of Pop-town.net main page is 2.9 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 34.9 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 34.9 kB or 79% of the original size.
Potential reduce by 168.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. Pop Town images are well optimized though.
Potential reduce by 99.1 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 99.1 kB or 65% of the original size.
Potential reduce by 19.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. Pop-town.net needs all CSS files to be minified and compressed as it can save up to 19.9 kB or 82% of the original size.
Number of requests can be reduced by 26 (23%)
113
87
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pop Town. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
pop-town.net
1639 ms
format.css
705 ms
contents.css
372 ms
topage_new.css
440 ms
wideslider.css
457 ms
jquery.lightbox-0.5.css
423 ms
jquery.js
870 ms
jquery.lightbox-0.5.js
946 ms
jcarousellite.js
634 ms
swfobject_modified.js
1120 ms
jquery.easing.js
886 ms
ga.js
34 ms
20160316flimg51_0_0.jpgf.jpg
2644 ms
20160317flimg51_1_0.jpgf.jpg
2644 ms
20160317flimg51_2_0.jpgf.jpg
2650 ms
20160316flimg51_2_0.jpgf.jpg
2667 ms
20160316flimg51_3_0.jpgf.jpg
3465 ms
20160316flimg51_4_0.jpgf.jpg
2801 ms
mainbg_new.jpg
175 ms
logomark.gif
444 ms
head_copy.gif
322 ms
title_event.jpg
321 ms
arrow_left.gif
322 ms
spacer.gif
280 ms
arrow_right.gif
353 ms
title_topics.jpg
574 ms
title_shopnews.jpg
494 ms
btn_parking.jpg
996 ms
btn_leasing.jpg
996 ms
title_info.gif
520 ms
btn_keihan.jpg
672 ms
btn_fb.gif
792 ms
btn_concert.jpg
995 ms
btn_eknet.jpg
997 ms
btn_cospa.jpg
998 ms
banner_bunka.jpg
997 ms
title_timesche.gif
1161 ms
btn_time.jpg
1196 ms
logofooter.gif
1409 ms
copyright.gif
1205 ms
sdk.js
210 ms
20160319evt602_list.jpgindex.jpg
2806 ms
20160319evt601_list.jpgindex.jpg
2790 ms
20160317evt600_list.jpgindex.jpg
2815 ms
20160317evt599_list.jpgindex.jpg
2831 ms
20160317evt598_list.jpgindex.jpg
2980 ms
20160312evt597_list.jpgindex.jpg
2988 ms
20160319shp1762_1.jpgindex.jpg
2978 ms
20160319shp1761_1.jpgindex.jpg
2987 ms
20160319shp1760_1.jpgindex.jpg
3024 ms
20160319shp1759_1.jpgindex.jpg
3178 ms
20160319shp1758_1.jpgindex.jpg
3156 ms
20160317shp1755_1.jpgindex.jpg
3191 ms
subnavi.jpg
1344 ms
navi_bg_white.jpg
1148 ms
glovalnavi.jpg
1808 ms
arrow.gif
1335 ms
widgets.js
83 ms
__utm.gif
52 ms
20160316flimg51_0_0.jpgfb.jpg
3007 ms
20160317flimg51_1_0.jpgfb.jpg
3067 ms
20160317flimg51_2_0.jpgfb.jpg
3171 ms
20160316flimg51_2_0.jpgfb.jpg
3190 ms
20160316flimg51_3_0.jpgfb.jpg
3235 ms
20160316flimg51_4_0.jpgfb.jpg
3222 ms
foot_btn01.gif
1233 ms
bg_foot.gif
1251 ms
arrow_footer.gif
1374 ms
arrow_left.png
1395 ms
arrow_right.png
1431 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
169 ms
96 ms
xd_arbiter.php
168 ms
xd_arbiter.php
303 ms
syndication
106 ms
317215303891304448
210 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
169 ms
382731f2879c8bae549dbb9c6982b22e_normal.jpeg
345 ms
Cd5JzevUMAA4a13.jpg:small
351 ms
Cd4-nfsVAAAHEKp.jpg:small
350 ms
Cd4di16UAAALuNo.jpg:small
346 ms
Cd4GTGXVAAAoC8P.jpg:small
351 ms
Cd33fY2UUAATy5j.jpg:small
349 ms
CdzX283UsAEcO7Q.jpg:small
351 ms
CdzCcnIUIAAInCx.jpg:small
369 ms
CdvTUjYUsAAfCy4.jpg:small
369 ms
Cduni_SUUAEw4hV.jpg:small
371 ms
CdtxEaSVIAEmINF.jpg:small
371 ms
Cd-bULGUUAEjcI8.jpg:small
368 ms
Cd-bUeVUsAAxeUg.jpg:small
381 ms
Cd9GuDLUUAEorKV.jpg:small
404 ms
Cd9Gt8rUEAECt17.jpg:small
397 ms
Cd5xi3zVIAAd299.jpg:small
371 ms
Cd5xi1DUkAAUZMr.jpg:small
406 ms
Cd5xiwVUsAAYXsY.jpg:small
434 ms
Cd5hr82UUAIENFj.jpg:small
371 ms
Cd5hsK4UMAE_jJh.jpg:small
401 ms
Cd42k6EUYAEnnv3.jpg:small
380 ms
Cd42k5aUUAAspGl.jpg:small
428 ms
Cd42k8IUYAEdTF9.jpg:small
438 ms
Cd4Rc8VUEAQUjw3.jpg:small
409 ms
Cd4RdA6UsAE2WDD.jpg:small
452 ms
Cd4RdA3UIAAGLiA.jpg:small
451 ms
Cd4RdGUVAAQOG8q.jpg:small
458 ms
Cdy-wjoUEAASKeE.jpg:small
476 ms
Cdy-wCAUEAAWv1Z.jpg:small
473 ms
Cdy9bJPUMAIRrII.jpg:small
440 ms
Cdy9bqdUMAAXjw6.jpg:small
482 ms
CduweDDUsAArYdf.jpg:small
454 ms
CduwebSVIAA-Urf.jpg:small
499 ms
CduJd4TUsAAmsjv.jpg:small
456 ms
CduJdzGVAAIFZ4R.jpg:small
567 ms
jot
26 ms
pop-town.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Links do not have a discernible name
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.
pop-town.net 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
pop-town.net 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pop-town.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pop-town.net 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.
pop-town.net
Open Graph description is not detected on the main page of Pop Town. 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: