3.8 sec in total
810 ms
2.5 sec
472 ms
Visit leye.jp now to see the best up-to-date Leye content and also check out these interesting facts you probably never knew about leye.jp
スマートフォン顕微鏡 Leye (エルアイ) の製品紹介。
Visit leye.jpWe analyzed Leye.jp page load time and found that the first response time was 810 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
leye.jp performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value7.3 s
5/100
25%
Value5.5 s
55/100
10%
Value220 ms
87/100
30%
Value0.102
89/100
15%
Value6.1 s
63/100
10%
810 ms
509 ms
6 ms
523 ms
355 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 52% of them (22 requests) were addressed to the original Leye.jp, 12% (5 requests) were made to Platform.twitter.com and 10% (4 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Leye.jp.
Page size can be reduced by 146.4 kB (50%)
295.5 kB
149.1 kB
In fact, the total size of Leye.jp main page is 295.5 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. 50% of websites need less resources to load. CSS take 132.3 kB which makes up the majority of the site volume.
Potential reduce by 11.9 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 5.3 kB, which is 36% 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 11.9 kB or 80% of the original size.
Potential reduce by 6.3 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. Leye images are well optimized though.
Potential reduce by 16.0 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 16.0 kB or 66% of the original size.
Potential reduce by 112.2 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. Leye.jp needs all CSS files to be minified and compressed as it can save up to 112.2 kB or 85% of the original size.
Number of requests can be reduced by 13 (32%)
41
28
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
leye.jp
810 ms
leye-jqm-1.3.2.min.css
509 ms
jquery.mobile.structure-1.3.2.min.css
6 ms
magnific-popup.css
523 ms
app.css
355 ms
jquery-1.10.2.min.js
11 ms
jquery.magnific-popup.min.js
725 ms
app.js
364 ms
jquery.mobile-1.3.2.min.js
10 ms
leye_logo_pc.png
194 ms
movie01.jpg
371 ms
movie02.jpg
573 ms
concept01.png
565 ms
concept02.png
526 ms
concept03.png
565 ms
punch01.jpg
364 ms
punch02.jpg
539 ms
punch03.jpg
733 ms
terabase_logo.png
699 ms
cloverflavor_logo.png
703 ms
okazaemon.png
745 ms
widgets.js
93 ms
ajax-loader.gif
656 ms
main_visual_pc_01.jpg
1007 ms
main_visual_pc_02.png
777 ms
icons-18-white.png
778 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
131 ms
syndication
95 ms
473692083308351488
187 ms
proxy.jpg
97 ms
proxy.jpg
88 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
74 ms
VuapX08M_normal.png
156 ms
BzUABQXCIAA0CcW.jpg
160 ms
By1jh8RCYAI0lQr.jpg
226 ms
BwN0q26CYAESBsN.jpg:large
268 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
54 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
149 ms
proxy.jpg
45 ms
proxy.jpg
37 ms
jot.html
31 ms
leye.jp accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
leye.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
leye.jp SEO score
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
Document uses legible font sizes
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leye.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 Leye.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.
leye.jp
Open Graph description is not detected on the main page of Leye. 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: