Tools & Wizards About Us

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

vokka.jp

VOKKA [ヴォッカ] ｜ いまより少し良い毎日を

Page Load Speed

7.5 sec in total

First Response

555 ms

Resources Loaded

5 sec

Page Rendered

1.9 sec

About Website

Click here to check amazing VOKKA content for Japan. Otherwise, check out these important facts you probably never knew about vokka.jp

VOKKAは、いまより少し良い毎日をすごしたい人のためのライフスタイルメディアです。メンズファッション・レディースファッション・グルメ・料理・車・映画・音楽・旅行・レジャー・フィットネスなど、毎日をいまより少し良くするための情報を提供しています。

Visit vokka.jp

Key Findings

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

Performance Metrics

vokka.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value8,350 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.469

18/100

15%

TTI (Time to Interactive)

Value30.0 s

0/100

10%

Network Requests Diagram

vokka.jp

555 ms

vokka.jp

833 ms

pc-b9f86e86.css

158 ms

ads-61c165581bbeef2dcd2e.js

311 ms

adsbygoogle.js

220 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 11% of them (10 requests) were addressed to the original Vokka.jp, 69% (60 requests) were made to Img.vokka.jp and 3% (3 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Img.vokka.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 237.8 kB (28%)

Content Size

843.8 kB

After Optimization

606.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vokka.jp main page is 843.8 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. 70% of websites need less resources to load. Javascripts take 455.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 220.9 kB

  • Original 263.1 kB
  • After minification 263.1 kB
  • After compression 42.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 220.9 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 5.7 kB

  • Original 95.0 kB
  • After minification 89.3 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. VOKKA images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.4 kB

  • Original 455.9 kB
  • After minification 455.9 kB
  • After compression 450.6 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

-19%

Potential reduce by 5.8 kB

  • Original 29.7 kB
  • After minification 29.7 kB
  • After compression 23.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. Vokka.jp needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

84

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

vokka.jp accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

vokka.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

vokka.jp SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Vokka.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 Vokka.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 data is detected on the main page of VOKKA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: