7.4 sec in total
752 ms
6.5 sec
109 ms
Click here to check amazing Prty content for Hong Kong. Otherwise, check out these important facts you probably never knew about prty.jp
最新のテクノロジーとナラティブを融合させた空間と体験のコンセプトメイキング・デザイン・開発を行っています。
Visit prty.jpWe analyzed Prty.jp page load time and found that the first response time was 752 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
prty.jp performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value39.9 s
0/100
25%
Value9.7 s
11/100
10%
Value660 ms
45/100
30%
Value0.007
100/100
15%
Value8.8 s
35/100
10%
752 ms
1324 ms
344 ms
362 ms
1099 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 95% of them (36 requests) were addressed to the original Prty.jp, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Prty.jp.
Page size can be reduced by 260.8 kB (13%)
2.0 MB
1.7 MB
In fact, the total size of Prty.jp main page is 2.0 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. 15% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 4.5 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 893 B, 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 4.5 kB or 67% of the original size.
Potential reduce by 10.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. Prty images are well optimized though.
Potential reduce by 100.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 100.1 kB or 61% of the original size.
Potential reduce by 145.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. Prty.jp needs all CSS files to be minified and compressed as it can save up to 145.9 kB or 84% of the original size.
Number of requests can be reduced by 13 (35%)
37
24
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
prty.jp
752 ms
bootstrap.min.css
1324 ms
stylesheet.css
344 ms
stylesheet.css
362 ms
party.css
1099 ms
logo.svg
379 ms
jquery.js
1309 ms
bootstrap.min.js
995 ms
classie.js
562 ms
cbpAnimatedHeader.js
550 ms
util.js
893 ms
model.js
917 ms
carousel_controller.js
1232 ms
index_controller.js
1264 ms
header_controller.js
1280 ms
footer_controller.js
1344 ms
landing_copy.svg
1887 ms
lineto-akkurat-light.woff
968 ms
18820f9e-d51e-43be-9d0f-e510d9d1878a.woff
2777 ms
lineto-akkurat-regular.woff
984 ms
6e9eb620-9339-4b2e-bb9b-d514def96de7.woff
3073 ms
ga.js
30 ms
801 ms
1307 ms
foot_twitter.svg
1152 ms
foot_fb.svg
1149 ms
foot_instagram.svg
1163 ms
foot_blog.svg
1505 ms
__utm.gif
12 ms
GP_pweb_1_750x750.jpg
1728 ms
yoko_sp1-750x750.jpg
1287 ms
bz_02_shuchu_movielogo_PR_750x750.jpg
2493 ms
nrt_750.jpg
2390 ms
kirin-ow_thumb.jpg
3590 ms
1944 ms
Blog_Eyecatch_896x504_remo-on-375x211.jpg
2018 ms
Blog_Eyecatch_HYS_896x504-375x211.jpg
2494 ms
Blog_Eyecatch_YamaMiya-375x211.jpg
669 ms
prty.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
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.
prty.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
General
Impact
Issue
Detected JavaScript libraries
prty.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 uses legible font sizes
Tap targets are not sized appropriately
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prty.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Prty.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.
prty.jp
Open Graph description is not detected on the main page of Prty. 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: