Tools & Wizards About Us
eyem.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

eyem.jp

三重県松阪のまつ毛パーマならeyem | 相談しやすいプライベートサロン

Page Load Speed

6.6 sec in total

First Response

723 ms

Resources Loaded

5.7 sec

Page Rendered

220 ms

eyem.jp screenshot

About Website

Click here to check amazing Eyem content. Otherwise, check out these important facts you probably never knew about eyem.jp

松阪のプライベートサロンでは、まつ毛パーマとアイブロウの施術を通じてお客様の美しさを引き出します。丁寧なカウンセリングに基づく柔軟な提案で、理想の目元を実現します。

Visit eyem.jp

Key Findings

We analyzed Eyem.jp page load time and found that the first response time was 723 ms and then it took 5.9 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

eyem.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value32.2 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value730 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.917

3/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

eyem.jp

723 ms

css

51 ms

css

66 ms

font-awesome.min.css

48 ms

animate.css

857 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 79% of them (26 requests) were addressed to the original Eyem.jp, 6% (2 requests) were made to Fonts.googleapis.com and 3% (1 request) were made to Stackpath.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Eyem.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 491.0 kB (22%)

Content Size

2.3 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 12.5 kB

  • Original 15.3 kB
  • After minification 7.8 kB
  • After compression 2.8 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 7.5 kB, which is 49% 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 12.5 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 40.1 kB

  • Original 1.6 MB
  • After minification 1.5 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. Eyem images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 332.4 kB

  • Original 548.8 kB
  • After minification 538.4 kB
  • After compression 216.5 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 332.4 kB or 61% of the original size.

CSS Optimization

-89%

Potential reduce by 106.1 kB

  • Original 119.5 kB
  • After minification 91.9 kB
  • After compression 13.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. Eyem.jp needs all CSS files to be minified and compressed as it can save up to 106.1 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (74%)

Requests Now

31

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyem. 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 from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

eyem.jp

eyem.jp

723 ms

css

css

51 ms

css

css

66 ms

font-awesome.min.css

font-awesome.min.css

48 ms

animate.css

animate.css

857 ms

owl.carousel.min.css

owl.carousel.min.css

332 ms

owl.theme.default.min.css

owl.theme.default.min.css

352 ms

magnific-popup.css

magnific-popup.css

352 ms

flaticon.css

flaticon.css

354 ms

style.css

style.css

944 ms

jquery.min.js

jquery.min.js

1782 ms

jquery-migrate-3.0.1.min.js

jquery-migrate-3.0.1.min.js

526 ms

popper.min.js

popper.min.js

700 ms

bootstrap.min.js

bootstrap.min.js

1058 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

701 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

875 ms

jquery.stellar.min.js

jquery.stellar.min.js

876 ms

owl.carousel.min.js

owl.carousel.min.js

1176 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1051 ms

jquery.animateNumber.min.js

jquery.animateNumber.min.js

1051 ms

scrollax.min.js

scrollax.min.js

1130 ms

js

js

164 ms

google-map.js

google-map.js

1225 ms

main.js

main.js

1225 ms

js

js

53 ms

vaafb692b2aea4879b33c060e79fe94621666317369993

vaafb692b2aea4879b33c060e79fe94621666317369993

112 ms

home_5.png

home_5.png

283 ms

screen_shot_5.png

screen_shot_5.png

4148 ms

AppStore.png

AppStore.png

387 ms

GooglePlay.png

GooglePlay.png

451 ms

screen_shot_8.png

screen_shot_8.png

2375 ms

screen_shot_7.png

screen_shot_7.png

1517 ms

font

font

21 ms

Accessibility Review

eyem.jp accessibility score

79

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

eyem.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

eyem.jp 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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyem.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Eyem.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

eyem.jp

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