8.4 sec in total
381 ms
7.8 sec
206 ms
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.jpWe 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.
freshlook.jp performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value20.4 s
0/100
25%
Value11.3 s
5/100
10%
Value1,040 ms
25/100
30%
Value0.151
75/100
15%
Value18.7 s
3/100
10%
381 ms
546 ms
356 ms
357 ms
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 size can be reduced by 658.0 kB (44%)
1.5 MB
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.
Potential reduce by 15.6 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.
Potential reduce by 30.7 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.
Potential reduce by 578.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 578.5 kB or 75% of the original size.
Potential reduce by 33.1 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.
Number of requests can be reduced by 45 (41%)
110
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.
freshlook.jp
381 ms
www.freshlook.jp
546 ms
common.css
356 ms
top.css
357 ms
jquery-1.7.1.js
1572 ms
jquery.rollover.js
363 ms
jquery.cookie.js
371 ms
smoothScroll.js
555 ms
jquery.tile.js
701 ms
clicktag.js
713 ms
common.js
727 ms
jquery.easing.1.3.js
724 ms
jquery.timers.js
898 ms
ovr.js
1054 ms
widgets.js
79 ms
ga.js
7 ms
print.css
195 ms
favorite.pl
325 ms
__utm.gif
38 ms
logo.gif
345 ms
lab_fontsize.gif
344 ms
btn_fontsize_small.gif
351 ms
btn_fontsize_def.gif
374 ms
btn_fontsize_big.gif
386 ms
img_header_ope.gif
551 ms
img_header_tel.gif
698 ms
btn_shopsearch.jpg
708 ms
tab_gnavi1.jpg
716 ms
tab_gnavi2.jpg
744 ms
tab_gnavi3.jpg
752 ms
tab_gnavi4.jpg
910 ms
tab_gnavi5.jpg
1077 ms
tab_gnavi6.jpg
1106 ms
top_mainimg01.jpg
1717 ms
top_mainimg02.jpg
1488 ms
top_stit01.jpg
1156 ms
top_freet_btn.gif
1250 ms
top_stit02.gif
1420 ms
top_voices_btn.gif
1452 ms
top_relay.jpg
2174 ms
top_stit03.gif
1628 ms
new_ic.jpg
1769 ms
bg_arrow_pink.gif
1841 ms
top_stit04.gif
1836 ms
top_faq_btn.gif
2013 ms
top_stit05.gif
2059 ms
top_anzen.jpg
2142 ms
top_chisiki.jpg
2205 ms
top_howtouse2.jpg
2209 ms
top_hitominavi.jpg
2542 ms
top_beginner.gif
2579 ms
top_smt.gif
2740 ms
top_mb.gif
2708 ms
img_top.gif
2549 ms
like.php
103 ms
entry.js
769 ms
qeKvIRsJabD.js
293 ms
LVx-xkvaJ0b.png
330 ms
icon_othersite.gif
2409 ms
mixi_check_entry.css
10 ms
errorreport.production.js
295 ms
json.js
296 ms
underscore-string-1.3.3-2.0.0-compress.js
297 ms
namespace-brook-compress.js
303 ms
prototype-effects-1.6.1-1.8.3-compress.js
445 ms
mixi.js
307 ms
plugins.js
308 ms
favorite.production.js
582 ms
jquery-1.7.1.min-noconflict-compress.js
736 ms
icon_othersite_b.gif
2544 ms
img_footer_logo1.gif
2564 ms
img_footer_logo2.jpg
2563 ms
bg_gnavi.jpg
2560 ms
bg_top.jpg
3000 ms
top_box_bgline01.gif
2531 ms
top_freet_bg.jpg
2544 ms
top_voices_bg.gif
2571 ms
top_new_bg.gif
2584 ms
top_faq_bg.gif
2617 ms
top_aqua_bg.gif
2681 ms
analytics.js
4 ms
comment001.gif
7 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
126 ms
actag
356 ms
bg_footer_bottom.gif
2686 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
49 ms
favorite_button003-.png
8 ms
comment_content_top001.gif
7 ms
bg_footer_top.gif
2551 ms
tab_gnavi1_on.jpg
2579 ms
jot
98 ms
tab_gnavi2_on.jpg
2569 ms
tab_gnavi3_on.jpg
2504 ms
tab_gnavi4_on.jpg
2408 ms
tab_gnavi5_on.jpg
2505 ms
tab_gnavi6_on.jpg
2542 ms
top_mainimg01_on.jpg
3058 ms
top_mainimg02_on.jpg
2804 ms
top_freet_btn_on.gif
2354 ms
top_voices_btn_on.gif
2386 ms
top_relay_on.jpg
2879 ms
top_faq_btn_on.gif
2385 ms
top_anzen_on.jpg
2432 ms
top_chisiki_on.jpg
2418 ms
top_howtouse2_on.jpg
2557 ms
top_hitominavi_on.jpg
2628 ms
top_beginner_on.gif
2845 ms
img_top_on.gif
2372 ms
btn_shopsearch_on.jpg
2476 ms
btn_fontsize_def_on.gif
193 ms
btn_fontsize_small_on.gif
334 ms
btn_fontsize_big_on.gif
339 ms
freshlook.jp accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[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
<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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
freshlook.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
freshlook.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 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.
freshlook.jp
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: