Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

jiparty.com

Tokyo International Party 東京インターナショナルパーティー

Page Load Speed

4.3 sec in total

First Response

776 ms

Resources Loaded

3.1 sec

Page Rendered

511 ms

jiparty.com screenshot

About Website

Visit jiparty.com now to see the best up-to-date Ji Party content and also check out these interesting facts you probably never knew about jiparty.com

東京の六本木で毎月開催されるインターナショナルパーティー。An international party held monthly in Roppongi, Tokyo, Japan.

Visit jiparty.com

Key Findings

We analyzed Jiparty.com page load time and found that the first response time was 776 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

jiparty.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value8.1 s

20/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

jiparty.com

776 ms

style.css

349 ms

spods.js

1944 ms

ga.js

46 ms

bg.gif

179 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 82% of them (23 requests) were addressed to the original Jiparty.com, 7% (2 requests) were made to Google-analytics.com and 7% (2 requests) were made to D2etxn1uda9tyh.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Cache.meta4-group.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.2 kB (11%)

Content Size

162.6 kB

After Optimization

145.4 kB

In fact, the total size of Jiparty.com main page is 162.6 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. 15% of websites need less resources to load. Images take 124.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 10.6 kB

  • Original 13.8 kB
  • After minification 13.7 kB
  • After compression 3.1 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 10.6 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 777 B

  • Original 124.9 kB
  • After minification 124.1 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. Ji Party images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

CSS Optimization

-85%

Potential reduce by 5.7 kB

  • Original 6.7 kB
  • After minification 2.9 kB
  • After compression 986 B

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. Jiparty.com needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

27

After Optimization

27

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ji Party. According to our analytics all requests are already optimized.

Accessibility Review

jiparty.com accessibility score

94

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

jiparty.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

jiparty.com SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jiparty.com 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 Jiparty.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Ji Party. 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: