Tools & Wizards About Us
vivid-eyes.com screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

vivid-eyes.com

Page Load Speed

4.3 sec in total

First Response

734 ms

Resources Loaded

3.1 sec

Page Rendered

441 ms

vivid-eyes.com screenshot

About Website

Visit vivid-eyes.com now to see the best up-to-date Vivid Eyes content and also check out these interesting facts you probably never knew about vivid-eyes.com

プラセンタ美容液のおすすめランキングをご紹介。口コミでおすすめの一番人気プラセンタ美容液ならこれ。効果や価格の違いをランキング形式でご紹介しています。

Visit vivid-eyes.com

Key Findings

We analyzed Vivid-eyes.com page load time and found that the first response time was 734 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

vivid-eyes.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

54/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

vivid-eyes.com

734 ms

jquery.min.js

83 ms

config.js

340 ms

styles.css

677 ms

textstyles.css

354 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 52% of them (17 requests) were addressed to the original Vivid-eyes.com, 27% (9 requests) were made to Asumi.shinobi.jp and 6% (2 requests) were made to X5.hishaku.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Vivid-eyes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.0 kB (26%)

Content Size

358.4 kB

After Optimization

263.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vivid-eyes.com main page is 358.4 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 240.4 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 15.2 kB

  • Original 22.7 kB
  • After minification 22.7 kB
  • After compression 7.6 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 15.2 kB or 67% of the original size.

Image Optimization

-0%

Potential reduce by 912 B

  • Original 240.4 kB
  • After minification 239.5 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. Vivid Eyes images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 5.3 kB

  • Original 9.5 kB
  • After minification 9.5 kB
  • After compression 4.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 5.3 kB or 56% of the original size.

CSS Optimization

-86%

Potential reduce by 73.6 kB

  • Original 85.7 kB
  • After minification 67.8 kB
  • After compression 12.1 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. Vivid-eyes.com needs all CSS files to be minified and compressed as it can save up to 73.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (59%)

Requests Now

32

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vivid-eyes.com

vivid-eyes.com

734 ms

jquery.min.js

jquery.min.js

83 ms

config.js

config.js

340 ms

styles.css

styles.css

677 ms

textstyles.css

textstyles.css

354 ms

10370040C

10370040C

529 ms

header.jpg

header.jpg

1241 ms

tables.css

tables.css

334 ms

commonstyles.css

commonstyles.css

359 ms

Zen

Zen

337 ms

encount

encount

504 ms

trac.js

trac.js

480 ms

assault

assault

515 ms

assault

assault

538 ms

headerbox_inner_bg.gif

headerbox_inner_bg.gif

334 ms

header_bg.gif

header_bg.gif

345 ms

column_bg.gif

column_bg.gif

364 ms

h3_bg.gif

h3_bg.gif

362 ms

h3.gif

h3.gif

365 ms

whatsnew_title.gif

whatsnew_title.gif

695 ms

menubox_bg.gif

menubox_bg.gif

724 ms

menu_bg.png

menu_bg.png

698 ms

pagetop_button.gif

pagetop_button.gif

705 ms

footlinkbox_bg.gif

footlinkbox_bg.gif

745 ms

1.13.17

1.13.17

479 ms

cookiesync

cookiesync

515 ms

fire

fire

179 ms

sync

sync

169 ms

248

248

158 ms

fire

fire

175 ms

track

track

186 ms

track

track

330 ms

track

track

336 ms

Accessibility Review

vivid-eyes.com accessibility score

86

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

Document doesn't have a <title> element

High

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

Best Practices

vivid-eyes.com 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

High

Page has valid source maps

SEO Factors

vivid-eyes.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vivid-eyes.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Vivid-eyes.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

vivid-eyes.com

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