Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

invogue.co.jp

Vogaro株式会社 - ヴォガロ株式会社

Page Load Speed

8.7 sec in total

First Response

621 ms

Resources Loaded

7.4 sec

Page Rendered

739 ms

invogue.co.jp screenshot

About Website

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

Vogaroは「流行を創出する」をミッションに、数々の企業のブランディング・マーケティング支援を展開するブランドマーケティングカンパニーです。

Visit invogue.co.jp

Key Findings

We analyzed Invogue.co.jp page load time and found that the first response time was 621 ms and then it took 8.1 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

invogue.co.jp performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

invogue.co.jp

621 ms

www.vogaro.co.jp

857 ms

common.head.js

439 ms

css

69 ms

global.css

576 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Invogue.co.jp, 50% (57 requests) were made to Vogaro.co.jp and 18% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Togalu.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (21%)

Content Size

7.0 MB

After Optimization

5.6 MB

In fact, the total size of Invogue.co.jp main page is 7.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. 70% of websites need less resources to load. Images take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 33.7 kB

  • Original 44.6 kB
  • After minification 43.6 kB
  • After compression 10.9 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 33.7 kB or 76% of the original size.

Image Optimization

-16%

Potential reduce by 1.0 MB

  • Original 6.4 MB
  • After minification 5.4 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. Obviously, Invogue needs image optimization as it can save up to 1.0 MB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 315.5 kB

  • Original 452.7 kB
  • After minification 432.9 kB
  • After compression 137.2 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 315.5 kB or 70% of the original size.

CSS Optimization

-84%

Potential reduce by 49.6 kB

  • Original 58.8 kB
  • After minification 42.0 kB
  • After compression 9.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. Invogue.co.jp needs all CSS files to be minified and compressed as it can save up to 49.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (37%)

Requests Now

108

After Optimization

68

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

Accessibility Review

invogue.co.jp accessibility score

73

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

Buttons do not have an accessible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

invogue.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

invogue.co.jp SEO score

100

Search Engine Optimization Advices

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 uses legible font sizes

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