9.5 sec in total
1.2 sec
8 sec
290 ms
Click here to check amazing P ARK content for Japan. Otherwise, check out these important facts you probably never knew about p-ark.co.jp
Visit p-ark.co.jpWe analyzed P-ark.co.jp page load time and found that the first response time was 1.2 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
p-ark.co.jp performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value10.7 s
0/100
25%
Value22.7 s
0/100
10%
Value7,070 ms
0/100
30%
Value0
100/100
15%
Value37.2 s
0/100
10%
1242 ms
516 ms
1031 ms
712 ms
737 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 64% of them (57 requests) were addressed to the original P-ark.co.jp, 21% (19 requests) were made to Static.xx.fbcdn.net and 11% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain P-ark.co.jp.
Page size can be reduced by 252.4 kB (9%)
2.8 MB
2.5 MB
In fact, the total size of P-ark.co.jp main page is 2.8 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. 35% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 18.3 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 18.3 kB or 76% of the original size.
Potential reduce by 79.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. P ARK images are well optimized though.
Potential reduce by 121.5 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 121.5 kB or 64% of the original size.
Potential reduce by 33.2 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. P-ark.co.jp needs all CSS files to be minified and compressed as it can save up to 33.2 kB or 82% of the original size.
Number of requests can be reduced by 42 (48%)
88
46
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of P ARK. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
p-ark.co.jp
1242 ms
init.css
516 ms
layout.css
1031 ms
widget.css
712 ms
style-index.css
737 ms
jquery.js
1656 ms
jquery-migrate.min.js
887 ms
jquery.easing.js
1080 ms
jquery.scrollTo.min.js
1073 ms
jquery.gotop.js
1068 ms
jquery.openwindow.js
1222 ms
inputval.js
1199 ms
gnav.js
1260 ms
google-search.js
1275 ms
jquery.cycle.js
2002 ms
slider.js
1391 ms
tab.js
1559 ms
plaza.js
1578 ms
ga.js
78 ms
main-img9.jpg
2185 ms
file_get_garden.php
1657 ms
file_get_plaza_feed.php
1386 ms
h-bg.png
333 ms
logo.gif
673 ms
hn-bg.gif
851 ms
hn.png
1392 ms
main-bg.gif
2034 ms
main-img1.jpg
3783 ms
main-img0.jpg
3084 ms
fla_btn04.jpg
2551 ms
fla_btn09.jpg
2858 ms
fla_btn08.jpg
3130 ms
fla_btn01.jpg
2818 ms
g-bg.png
2897 ms
home.png
3540 ms
pkun0.png
3548 ms
gn.png
3957 ms
border.jpg
3412 ms
sbk1-b.gif
3468 ms
sbk1-f.gif
3759 ms
buttons0.gif
4271 ms
button.gif
4441 ms
tn.gif
4120 ms
bk1-b.gif
4088 ms
bk1-f.gif
4136 ms
item-c.gif
4315 ms
item-new.gif
4464 ms
button2.png
4451 ms
f-bg0.gif
4454 ms
fn.png
4998 ms
gotop.png
4844 ms
f-bg1.gif
4767 ms
cpright.gif
4780 ms
main-img7.jpg
2452 ms
happy-park.jpg
2422 ms
sbk1-h.gif
1050 ms
img2.gif
2471 ms
img3.jpg
2701 ms
__utm.gif
25 ms
likebox.php
185 ms
hDvwL1_H7g-.css
84 ms
56WNbrUYLbL.css
107 ms
yZ--Yu0PDbV.css
126 ms
QD6_ejUFoCN.css
157 ms
q68gy-v_YMF.js
170 ms
FJmpeSpHpjS.js
185 ms
0wM5s1Khldu.js
140 ms
1bNoFZUdlYZ.js
141 ms
njO1TPvGzoR.js
143 ms
1QuX41zDRrx.js
164 ms
Oagsvfb4VWi.js
196 ms
LTv6ZK-5zxz.js
208 ms
1FCa-btixu2.js
199 ms
11873507_1066473836707877_4040661745643242821_n.jpg
141 ms
1474407_818797651475498_2928406797422281457_n.jpg
151 ms
10341588_1192599207428672_2201041171507501467_n.jpg
202 ms
12821396_1190588510963075_7513161749235240899_n.jpg
206 ms
12801339_1188081604547099_4749338799906104990_n.jpg
223 ms
12814478_1186991654656094_8092056059473617045_n.jpg
206 ms
12806233_1186991661322760_4842448437391543701_n.jpg
222 ms
12814350_1186434298045163_4771051864320529487_n.jpg
203 ms
12795499_1186434294711830_893288195559923348_n.jpg
219 ms
12809552_1186434291378497_6418357830248229263_n.jpg
220 ms
wL6VQj7Ab77.png
92 ms
s7jcwEQH7Sx.png
91 ms
QDwYpIaRyfG.png
93 ms
K00K-UgnsKu.png
93 ms
I6-MnjEovm5.js
21 ms
pQrUxxo5oQp.js
35 ms
p-ark.co.jp 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.
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
Links do not have a discernible name
p-ark.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
p-ark.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise P-ark.co.jp 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 P-ark.co.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.
p-ark.co.jp
Open Graph description is not detected on the main page of P ARK. 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: