7.6 sec in total
745 ms
6.1 sec
731 ms
Visit c-lensya.com now to see the best up-to-date C Lensya content and also check out these interesting facts you probably never knew about c-lensya.com
コンタクトの激安販売店、レンズ屋.comです。人気のエバーカラーワンデー、カラコン、使い捨てコンタクトレンズ、ケア用品などを通販でお探しなら是非ご利用ください。
Visit c-lensya.comWe analyzed C-lensya.com page load time and found that the first response time was 745 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
c-lensya.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value6.6 s
8/100
25%
Value5.0 s
64/100
10%
Value50 ms
100/100
30%
Value0.28
43/100
15%
Value9.5 s
30/100
10%
745 ms
334 ms
342 ms
157 ms
312 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 31% of them (49 requests) were addressed to the original C-lensya.com, 51% (82 requests) were made to Gigaplus.makeshop.jp and 2% (3 requests) were made to Sync.fout.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Gigaplus.makeshop.jp.
Page size can be reduced by 165.2 kB (5%)
3.4 MB
3.2 MB
In fact, the total size of C-lensya.com main page is 3.4 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. 60% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 80.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 11.5 kB, which is 11% 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 80.8 kB or 80% of the original size.
Potential reduce by 50.6 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. C Lensya images are well optimized though.
Potential reduce by 11.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 11.5 kB or 32% of the original size.
Potential reduce by 22.3 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. C-lensya.com needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 81% of the original size.
Number of requests can be reduced by 45 (29%)
157
112
The browser has sent 157 CSS, Javascripts, AJAX and image requests in order to completely render the main page of C Lensya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
c-lensya.com
745 ms
import.css
334 ms
script.js
342 ms
check_history.css
157 ms
pager.css
312 ms
shopdetail.css
314 ms
ranking.css
333 ms
basket.css
336 ms
security.css
342 ms
category_menu.css
508 ms
topicpath.css
642 ms
catalog.css
644 ms
count.makeshop.jp
542 ms
pmda_eyecare_bnr_l.jpg
413 ms
meriinovabr.gif
483 ms
meisai150.jpg
733 ms
0000000004182.jpg
1246 ms
0000000004202.jpg
1287 ms
0050000000462.jpg
1474 ms
doarileftmenu2.jpg
494 ms
donashi0001.jpg
496 ms
kyaria_150X60.jpg
510 ms
t-set-ber.gif
516 ms
otoku-no1-t.gif
522 ms
otoku-n1d-aqu-6-big-w465_b.jpg
1403 ms
otoku-n1d-aqu-12-big_b_w465.jpg
1160 ms
prime1d_6pset_bn_465X160.jpg
979 ms
otoku-no1-bar.gif
680 ms
otoku-n1d-ring-6-230X77_b.jpg
866 ms
otoku-n1d-ring-4-230X77_b.jpg
873 ms
otoku-n1d-aqu-6-230X77_b.jpg
1023 ms
otoku-n1d-aqu-4-230X77_b.jpg
1216 ms
otoku-1dfine-6-230X77_b.jpg
1227 ms
otoku-1dfine-4-230X77_b.gif
1141 ms
otoku-lconex-6p-230X77_b.gif
1195 ms
otoku-lconex-4-230X77.gif
1303 ms
otoku-2wfineuv-6-230X77_b.jpg
1317 ms
otoku-2wfineuv-4-230X77_b.gif
1369 ms
otoku-neo14-6-230X77_b.jpg
1392 ms
otoku-neo14-4-230X77_b.gif
1406 ms
otoku-mdp-6-230_b.jpg
1466 ms
otoku-md2-6-230_b.jpg
1476 ms
otoku-money-no1_b.gif
1541 ms
otoku-ring-6-big-w465_b.jpg
1920 ms
t-set-ber2.gif
1554 ms
Prime1day_bn_640.jpg
1799 ms
prime1d_bn_6pset.jpg
1802 ms
dailies_multi_bn.jpg
1639 ms
falin-bn-470X153.jpg
2053 ms
ao-sept-top_bn470.jpg
1710 ms
care_bn640.gif
1806 ms
bl-bn_150X150_pc.jpg
1867 ms
cv-bn_150X150_pc.jpg
1978 ms
ecom_bnr_800_300.jpg
2449 ms
head_img2.jpg
341 ms
head_img3.jpg
178 ms
head_img4.jpg
313 ms
head_img5.jpg
318 ms
head_img6.jpg
335 ms
head_img7.jpg
542 ms
head_img8.jpg
493 ms
head_img9.jpg
643 ms
head_img10.jpg
672 ms
head_img11.jpg
651 ms
head_img12.jpg
687 ms
head_img13.jpg
989 ms
head_img14.jpg
856 ms
head_img15.jpg
982 ms
head_img16.jpg
998 ms
head_img17.jpg
1025 ms
head_img18.jpg
1021 ms
head_img19.jpg
1186 ms
spacer.gif
1318 ms
menu.jpg
1319 ms
leftmenu-toku.gif
1328 ms
1day.jpg
1347 ms
2week.jpg
1349 ms
ranshi.jpg
1520 ms
1month.jpg
1655 ms
leftmenu-acu.jpg
1652 ms
leftmenu1.jpg
1660 ms
support.jpg
2068 ms
c-lensya_smp_top_QR.gif
1683 ms
sagawa.jpg
1828 ms
yamato.jpg
1970 ms
1daycaraeyen_bnr.jpg
473 ms
head_img1.jpg
1976 ms
is_show_gmo_header.html
898 ms
aq_tag_aos.js
186 ms
425 ms
renzu-foot.gif
1982 ms
ga.js
8 ms
__utm.gif
16 ms
spacer.gif
618 ms
EM34BYVZ46DUGEQNJE6A
140 ms
gmsync
302 ms
segmentation.js
28 ms
376 ms
ecomuv_bnr_640_256.jpg
1819 ms
640x200_sp2.jpg
1706 ms
sp_bnr640x200.jpg
1783 ms
cnt
353 ms
erouge_bnr_640_256.jpg
2186 ms
Ring_doublecolor_yoko_bn_470.jpg
2061 ms
Ringcolors_yoko_hazel3_bn_470.jpg
2145 ms
pop_bn_pc_470X243.jpg
1953 ms
dynrec2.js
328 ms
neocieluv_bnr_720.jpg
1741 ms
putia_bnr.jpg
1906 ms
naturali_bn_470X131.jpg
1770 ms
victoria1day_30mai_bnr470.jpg
1745 ms
dynrecs.do
359 ms
pienage_bnr470X150.jpg
1668 ms
coffert-bn.jpg
1662 ms
rank-t-1.gif
1675 ms
rank-b-1.gif
1703 ms
t-neo1d-aqu-140X140.jpg
1699 ms
rank-b-2.gif
1639 ms
t-lcon-140X140.jpg
1670 ms
rank-b-3.gif
1606 ms
t-neo14-140X140.jpg
1662 ms
rank-b-4.gif
1701 ms
t-1dfine-140X140.jpg
1679 ms
rank-b-5.gif
1638 ms
t-2wfine-140X140.jpg
1656 ms
rank-t-2.gif
1621 ms
rank-rd-1.gif
1679 ms
t-neo1d-r-140X140.jpg
1603 ms
rank-rd-2.gif
1560 ms
t-ever1d-n-140X140.jpg
1468 ms
rank-rd-3.gif
1484 ms
rank-rd-4.gif
1533 ms
t-coffret-140X140.jpg
1544 ms
rank-rd-5.gif
1482 ms
erouge_140140.jpg
1450 ms
rank-rd-6.gif
1391 ms
ciel_uv_140X140.jpg
1251 ms
rank-rd-7.gif
1245 ms
t-2wvuety-b-140X140.jpg
1274 ms
rank-rd-8.gif
1137 ms
t-2wvuety-s-140X140.jpg
1023 ms
t-pickup.gif
994 ms
t-naturalimg140X303.jpg
1157 ms
t-pickup-ber.gif
1035 ms
card.jpg
1031 ms
paidy_logo.png
1022 ms
kyaria.jpg
991 ms
beacon.html
12 ms
pixel
17 ms
cs
423 ms
Pug
20 ms
set
302 ms
sd
5 ms
tap.php
5 ms
sync
10 ms
pixel
15 ms
sync
353 ms
mapuser
150 ms
sync
210 ms
sync
199 ms
c-lensya.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
c-lensya.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
c-lensya.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise C-lensya.com 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 C-lensya.com main page’s claimed encoding is euc-jp. 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.
c-lensya.com
Open Graph description is not detected on the main page of C Lensya. 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: