Tools & Wizards About Us
vivi.tv screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

vivi.tv

【ViVi】公式デジタルマガジン(講談社)。自分らしく、かっこよく生きるZ世代のためのトレンドやお役立ち情報が満載！

Page Load Speed

3.8 sec in total

First Response

10 ms

Resources Loaded

2.9 sec

Page Rendered

904 ms

vivi.tv screenshot

About Website

Visit vivi.tv now to see the best up-to-date Vi content for Japan and also check out these interesting facts you probably never knew about vivi.tv

ファッション＆ビューティ、イケメン・占い・恋愛・ごはん＆旅の情報、こっそり知りたい◯◯など、自分らしく生きるZ世代のためのトレンド情報や、知っておくとちょっぴり人生に役立つ、キャリア・フェムケア・マネーなどの情報を毎日更新中

Visit vivi.tv

Key Findings

We analyzed Vivi.tv page load time and found that the first response time was 10 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

vivi.tv performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.642

9/100

15%

TTI (Time to Interactive)

Value43.9 s

0/100

10%

Network Requests Diagram

vivi.tv

10 ms

www.vivi.tv

1466 ms

app.css

28 ms

all.css

56 ms

swiper.min.css

53 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 36% of them (40 requests) were addressed to the original Vivi.tv, 32% (36 requests) were made to Res.cloudinary.com and 5% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Vivi.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (39%)

Content Size

5.7 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vivi.tv main page is 5.7 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. 75% 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 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 76.2 kB

  • Original 93.3 kB
  • After minification 78.1 kB
  • After compression 17.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. This page needs HTML code to be minified as it can gain 15.2 kB, which is 16% 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 76.2 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 65.4 kB

  • Original 2.7 MB
  • After minification 2.7 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. Vi images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 1.4 MB

  • Original 2.2 MB
  • After minification 2.2 MB
  • After compression 759.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 1.4 MB or 65% of the original size.

CSS Optimization

-93%

Potential reduce by 640.9 kB

  • Original 687.3 kB
  • After minification 300.2 kB
  • After compression 46.4 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. Vivi.tv needs all CSS files to be minified and compressed as it can save up to 640.9 kB or 93% of the original size.

Requests Breakdown

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

Requests Now

109

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vivi.tv

vivi.tv

10 ms

www.vivi.tv

www.vivi.tv

1466 ms

app.css

app.css

28 ms

all.css

all.css

56 ms

swiper.min.css

swiper.min.css

53 ms

otSDKStub.js

otSDKStub.js

52 ms

swiper.min.js

swiper.min.js

58 ms

gigya.js

gigya.js

97 ms

style.min.css

style.min.css

548 ms

css

css

44 ms

css

css

61 ms

css

css

70 ms

css

css

66 ms

87855853-b8f3-4c73-ad3c-d3fb1071667e.json

87855853-b8f3-4c73-ad3c-d3fb1071667e.json

64 ms

gtm.js

gtm.js

75 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

8 ms

location

location

136 ms

js

js

52 ms

analytics.js

analytics.js

21 ms

tag.js

tag.js

153 ms

otBannerSdk.js

otBannerSdk.js

29 ms

linkid.js

linkid.js

7 ms

collect

collect

118 ms

collect

collect

133 ms

collect

collect

116 ms

collect

collect

103 ms

common.js

common.js

13 ms

ranking.js

ranking.js

8 ms

top.js

top.js

534 ms

wp-embed.min.js

wp-embed.min.js

9 ms

vendor.js

vendor.js

14 ms

js

js

38 ms

top16.jpg

top16.jpg

192 ms

eye1.jpg

eye1.jpg

212 ms

top22.jpg

top22.jpg

282 ms

eye2.jpg

eye2.jpg

276 ms

top31.jpg

top31.jpg

277 ms

eye3.jpg

eye3.jpg

303 ms

top41.jpg

top41.jpg

298 ms

eye4.jpg

eye4.jpg

308 ms

top51.jpg

top51.jpg

308 ms

eye5.jpg

eye5.jpg

303 ms

EC30.jpg

EC30.jpg

305 ms

915.jpg

915.jpg

304 ms

eye-%E5%BE%A9%E5%85%833.jpg

eye-%E5%BE%A9%E5%85%833.jpg

306 ms

tw_244221.jpg

tw_244221.jpg

334 ms

eye29.jpg

eye29.jpg

333 ms

re_urakazuma5-tw.jpg

re_urakazuma5-tw.jpg

334 ms

EC6.jpg

EC6.jpg

336 ms

eye53.jpg

eye53.jpg

337 ms

sub14-1.png

sub14-1.png

338 ms

eye1.jpg

eye1.jpg

339 ms

ikemen_eye2024_chi1.jpg

ikemen_eye2024_chi1.jpg

341 ms

ikemen_eye2024_jap1.jpg

ikemen_eye2024_jap1.jpg

343 ms

natsume_tw.jpg

natsume_tw.jpg

377 ms

unmei_tw.jpg

unmei_tw.jpg

376 ms

kemurai_tw.jpg

kemurai_tw.jpg

376 ms

tw13.jpg

tw13.jpg

376 ms

tw.jpg

tw.jpg

378 ms

TW28.jpg

TW28.jpg

380 ms

tw18.jpg

tw18.jpg

420 ms

tw18.jpg

tw18.jpg

421 ms

shiratama_2023_top.jpg

shiratama_2023_top.jpg

419 ms

%E3%83%95%E3%82%9A%E3%83%AD%E3%82%B7%E3%82%99%E3%82%A7%E3%82%AF%E3%83%88_21.png

%E3%83%95%E3%82%9A%E3%83%AD%E3%82%B7%E3%82%99%E3%82%A7%E3%82%AF%E3%83%88_21.png

425 ms

%E3%82%A2%E3%82%A4%E3%82%AD%E3%83%A3%E3%83%83%E3%83%8111.jpg

%E3%82%A2%E3%82%A4%E3%82%AD%E3%83%A3%E3%83%83%E3%83%8111.jpg

380 ms

daifuku_vivitv_web_200416_2-1200x600-1.png

daifuku_vivitv_web_200416_2-1200x600-1.png

424 ms

%E3%81%B3%E3%81%B3%E7%8C%ABTOP.png

%E3%81%B3%E3%81%B3%E7%8C%ABTOP.png

423 ms

%E5%8D%A0%E3%81%84-ec.jpg

%E5%8D%A0%E3%81%84-ec.jpg

423 ms

icon_search.svg

icon_search.svg

25 ms

logo.svg

logo.svg

28 ms

icon_member.svg

icon_member.svg

27 ms

logo_side_menu_kodansha.svg

logo_side_menu_kodansha.svg

29 ms

heading_recommend.svg

heading_recommend.svg

25 ms

heading_new.svg

heading_new.svg

36 ms

heading_ranking.svg

heading_ranking.svg

33 ms

heading_comic.svg

heading_comic.svg

34 ms

heading_horoscope.svg

heading_horoscope.svg

31 ms

eye51.jpg

eye51.jpg

204 ms

TU_twittercard.jpg

TU_twittercard.jpg

273 ms

heading_saved.svg

heading_saved.svg

157 ms

heading_hot.svg

heading_hot.svg

159 ms

031.jpg

031.jpg

184 ms

cover202406.jpg

cover202406.jpg

267 ms

icon_addhome_iphone.svg

icon_addhome_iphone.svg

200 ms

icon_addhome_android.svg

icon_addhome_android.svg

198 ms

logo_footer.svg

logo_footer.svg

208 ms

logo_withonline.svg

logo_withonline.svg

207 ms

logo_voce.svg

logo_voce.svg

264 ms

logo_mimollet.svg

logo_mimollet.svg

270 ms

logo_frau.svg

logo_frau.svg

274 ms

icon_abjmark.svg

icon_abjmark.svg

279 ms

logo_footer_kodansha.svg

logo_footer_kodansha.svg

275 ms

fbevents.js

fbevents.js

206 ms

ope-mediaconsortium.js

ope-mediaconsortium.js

206 ms

tag.min.js

tag.min.js

261 ms

uwt.js

uwt.js

414 ms

icon_bookmark.svg

icon_bookmark.svg

258 ms

icon_line.svg

icon_line.svg

193 ms

icon_instagram.svg

icon_instagram.svg

197 ms

icon_x.svg

icon_x.svg

195 ms

icon_youtube.svg

icon_youtube.svg

202 ms

icon_tiktok.svg

icon_tiktok.svg

199 ms

cx.cce.js

cx.cce.js

130 ms

1229671800554878

1229671800554878

85 ms

cx.js

cx.js

70 ms

container-polyfills.js

container-polyfills.js

26 ms

beacon.min.js

beacon.min.js

175 ms

bi.js

bi.js

850 ms

sp1.html

sp1.html

16 ms

collect

collect

17 ms

sync

sync

19 ms

Accessibility Review

vivi.tv accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role] values are not valid

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

High

Links do not have a discernible 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>).

Best Practices

vivi.tv 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

vivi.tv SEO score

84

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

High

robots.txt is not valid

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

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 Vivi.tv 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 Vivi.tv 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

vivi.tv

Open Graph data is detected on the main page of Vi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: