Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

lensking.jp

コンタクトレンズ通販 レンズアップル

Page Load Speed

141 ms in total

First Response

23 ms

Resources Loaded

60 ms

Page Rendered

58 ms

lensking.jp screenshot

About Website

Welcome to lensking.jp homepage info - get ready to check Lensking best content for Japan right away, or after learning these important things about lensking.jp

コンタクトレンズ通販レンズアップルは、安心・便利なコンタクトレンズのオンラインショップです。ワンデーアキュビュー、デイリーズアクアの国内正規コンタクトレンズやケア用品を超特価でお届けします。

Visit lensking.jp

Key Findings

We analyzed Lensking.jp page load time and found that the first response time was 23 ms and then it took 118 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

lensking.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

lensking.jp

23 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Lensking.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (23 ms) belongs to the original domain Lensking.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 150.6 kB (10%)

Content Size

1.5 MB

After Optimization

1.3 MB

In fact, the total size of Lensking.jp main page is 1.5 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-53%

Potential reduce by 1.6 kB

  • Original 3.1 kB
  • After minification 3.0 kB
  • After compression 1.5 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 1.6 kB or 53% of the original size.

Image Optimization

-3%

Potential reduce by 39.2 kB

  • Original 1.3 MB
  • After minification 1.2 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. Lensking images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 64.9 kB

  • Original 121.0 kB
  • After minification 118.7 kB
  • After compression 56.1 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 64.9 kB or 54% of the original size.

CSS Optimization

-86%

Potential reduce by 44.9 kB

  • Original 51.9 kB
  • After minification 33.6 kB
  • After compression 7.0 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. Lensking.jp needs all CSS files to be minified and compressed as it can save up to 44.9 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

lensking.jp accessibility score

58

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

lensking.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 Lensking.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 Lensking.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 description is not detected on the main page of Lensking. 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: