Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

whitekey.co.jp

【公式】ホワイトキー|婚活パーティー初のAIマッチング搭載

Page Load Speed

9.5 sec in total

First Response

569 ms

Resources Loaded

8.5 sec

Page Rendered

453 ms

whitekey.co.jp screenshot

About Website

Visit whitekey.co.jp now to see the best up-to-date Whitekey content for Japan and also check out these interesting facts you probably never knew about whitekey.co.jp

婚活パーティーやお見合いパーティーならホワイトキー。東京をはじめ全国都市で毎日開催中!豊富な企画から理想の出逢いをお探しいただけます。15年以上の運営実績で平均カップル率45%!初めてご参加でも安心してお楽しみいただけます。

Visit whitekey.co.jp

Key Findings

We analyzed Whitekey.co.jp page load time and found that the first response time was 569 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

whitekey.co.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value26.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value33.5 s

0/100

10%

Network Requests Diagram

whitekey.co.jp

569 ms

whitekey.co.jp

1189 ms

import.css

557 ms

top.css

559 ms

colorbox.css

560 ms

Our browser made a total of 238 requests to load all elements on the main page. We found that 69% of them (165 requests) were addressed to the original Whitekey.co.jp, 9% (21 requests) were made to Static.xx.fbcdn.net and 5% (11 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Whitekey.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 263.6 kB (12%)

Content Size

2.2 MB

After Optimization

2.0 MB

In fact, the total size of Whitekey.co.jp main page is 2.2 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. 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 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 45.2 kB

  • Original 58.8 kB
  • After minification 52.6 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 6.3 kB, which is 11% 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 45.2 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 9.1 kB

  • Original 1.6 MB
  • After minification 1.6 MB

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. Whitekey images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 100.0 kB

  • Original 371.9 kB
  • After minification 359.6 kB
  • After compression 271.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 100.0 kB or 27% of the original size.

CSS Optimization

-56%

Potential reduce by 109.3 kB

  • Original 195.0 kB
  • After minification 162.8 kB
  • After compression 85.6 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. Whitekey.co.jp needs all CSS files to be minified and compressed as it can save up to 109.3 kB or 56% of the original size.

Requests Breakdown

Number of requests can be reduced by 77 (33%)

Requests Now

230

After Optimization

153

The browser has sent 230 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whitekey. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

whitekey.co.jp accessibility score

70

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

whitekey.co.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

whitekey.co.jp SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whitekey.co.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 Whitekey.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.

Social Sharing Optimization

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