Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

freshlook.jp

2週間・1カ月交換コンタクトレンズ| MyAlcon | Base

Page Load Speed

8.4 sec in total

First Response

381 ms

Resources Loaded

7.8 sec

Page Rendered

206 ms

freshlook.jp screenshot

About Website

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

アルコンのカラーコンタクトレンズ(カラコン) 「フレッシュルック® デイリーズ®」シリーズの公式サイトです。カラコンに関する情報や初めてでも安全に使う情報が満載。カラコンに合うファッションコーデも紹介!まずは無料でお試しできる「フリートライアル」へお気軽に!

Visit freshlook.jp

Key Findings

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

freshlook.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value20.4 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value1,040 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.151

75/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

freshlook.jp

381 ms

www.freshlook.jp

546 ms

common.css

356 ms

top.css

357 ms

jquery-1.7.1.js

1572 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 77% of them (86 requests) were addressed to the original Freshlook.jp, 8% (9 requests) were made to Plugins.mixi.jp and 4% (4 requests) were made to Img.mixi.net. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Freshlook.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 658.0 kB (44%)

Content Size

1.5 MB

After Optimization

839.1 kB

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

HTML Optimization

-73%

Potential reduce by 15.6 kB

  • Original 21.4 kB
  • After minification 19.7 kB
  • After compression 5.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. 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.6 kB or 73% of the original size.

Image Optimization

-5%

Potential reduce by 30.7 kB

  • Original 659.1 kB
  • After minification 628.4 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. Freshlook images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 578.5 kB

  • Original 775.8 kB
  • After minification 625.3 kB
  • After compression 197.4 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 578.5 kB or 75% of the original size.

CSS Optimization

-82%

Potential reduce by 33.1 kB

  • Original 40.6 kB
  • After minification 33.3 kB
  • After compression 7.5 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. Freshlook.jp needs all CSS files to be minified and compressed as it can save up to 33.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (41%)

Requests Now

110

After Optimization

65

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

Accessibility Review

freshlook.jp accessibility score

75

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

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

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

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

freshlook.jp best practices score

83

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

SEO Factors

freshlook.jp SEO score

92

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freshlook.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Freshlook.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 Freshlook. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: