9.9 sec in total
495 ms
8.1 sec
1.3 sec
Click here to check amazing Teacon content for United States. Otherwise, check out these important facts you probably never knew about teacon.jp
カラコンの激安通販と言えばTeAmo(ティアモ)公式!度あり・度なしのナチュラル系からハーフ系の種類豊富なカラコン&ソフトコンタクトも激安でご用意。
Visit teacon.jpWe analyzed Teacon.jp page load time and found that the first response time was 495 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
teacon.jp performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value10.8 s
0/100
25%
Value10.1 s
9/100
10%
Value1,780 ms
10/100
30%
Value0.063
97/100
15%
Value24.2 s
0/100
10%
495 ms
871 ms
1874 ms
1761 ms
1825 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Teacon.jp, 64% (65 requests) were made to Mtp7fmhigx4hy5.cdn.jp.idcfcloud.com and 3% (3 requests) were made to Spdmg.i-mobile.co.jp. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Mtp7fmhigx4hy5.cdn.jp.idcfcloud.com.
Page size can be reduced by 405.8 kB (4%)
10.0 MB
9.6 MB
In fact, the total size of Teacon.jp main page is 10.0 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. 55% of websites need less resources to load. Images take 9.7 MB which makes up the majority of the site volume.
Potential reduce by 47.1 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 7.4 kB, which is 12% 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 47.1 kB or 79% of the original size.
Potential reduce by 197.9 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. Teacon images are well optimized though.
Potential reduce by 146.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 146.0 kB or 57% of the original size.
Potential reduce by 14.7 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. Teacon.jp needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 77% of the original size.
Number of requests can be reduced by 37 (38%)
98
61
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teacon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
teacon.jp
495 ms
teacon.jp
871 ms
style.css
1874 ms
screen.css
1761 ms
order.css
1825 ms
jquery-1.9.1.min.js
2336 ms
flexcroll.js
2043 ms
modernizr.min.js
1866 ms
common.js
1915 ms
jquery.wideslider.min.js
2506 ms
wideslider.css
2046 ms
wideslider_reset.css
2017 ms
s_retargeting.js
922 ms
conversion.js
911 ms
adv.js
286 ms
pixel.js
633 ms
oct.js
128 ms
logo.png
283 ms
login_bt.png
181 ms
cart_bt.png
148 ms
2016_2_1day_sale_koushiki_top_pc.jpg
1800 ms
2015_1day_pc.jpg
1404 ms
2015_amoru_pc.jpg
1490 ms
2015_natural_pc.jpg
1521 ms
2015_vjinn_pc.jpg
1702 ms
2015_tough_pc.jpg
1800 ms
2015_darling_pc.jpg
2441 ms
2015_classy_pc.jpg
2218 ms
2015_tearly_pc.jpg
2893 ms
2015_Toujours_pc.jpg
2321 ms
mail_magazine.png
1979 ms
day-shipping_pc.jpg
2169 ms
free_shipping_pc.jpg
2161 ms
search.png
2343 ms
recommend_pc.png
2353 ms
2016_2_1day_sale_koushiki_series_pc.jpg
2511 ms
1day_ps_tksyu.jpg
2634 ms
ranking_br.png
2524 ms
ranking_1.png
2531 ms
ranking_2.png
2610 ms
ranking_3.png
2658 ms
a_145naturalblack.png
3063 ms
a_145classybrown.png
3072 ms
a_145amorebrown.png
3124 ms
recommendation_br.png
2788 ms
10_new_1day_chocola_series_pc.jpg
2949 ms
10_new_1day_shell_series_pc.jpg
3104 ms
main_toujour_pc.jpg
3234 ms
amoru_pc.jpg
3096 ms
main_natural_series.png
3425 ms
main_tough_series.png
3611 ms
main_vjinn_series.png
3388 ms
main_classy_series.png
3575 ms
main_tearly_series.png
3461 ms
main_darling_series.png
3471 ms
main_reprint_pc.jpg
3403 ms
analytics.js
51 ms
conversion.js
844 ms
collect
11 ms
collect
51 ms
822 ms
dg_gateway.js
290 ms
adv_inner.js
26 ms
2015_model_hinshitu_pc.png
2566 ms
blade_track_jp.js
898 ms
!WAVPzjd0Ejuhf!Cf8W9eg==
796 ms
2015_line_link_pc.jpg
2488 ms
browsing_br.png
2293 ms
no_deta.gif
2133 ms
news_br.png
2089 ms
permission.png
2125 ms
qr_code.png
2006 ms
pixel
318 ms
face_book.png
1822 ms
twitter.png
1875 ms
tamo_insta.jpg
1879 ms
credit.png
1829 ms
cookie_enabled_get.html
681 ms
combini.png
1808 ms
footer.png
1766 ms
Pug
90 ms
sync.ad-stir.com
619 ms
sync
53 ms
sync
1071 ms
is
721 ms
725 ms
fbds.js
181 ms
adsct
114 ms
adsct
115 ms
adv.aspx
933 ms
payment.png
1720 ms
sd
25 ms
pixel
20 ms
163 ms
prev.jpg
1679 ms
next.jpg
1740 ms
118 ms
bl_track.cgi
506 ms
dgcore.js
30 ms
adSiteVisit.js
50 ms
tr_adv.ashx
185 ms
25 ms
teacon.jp accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
teacon.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
teacon.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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teacon.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 Teacon.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.
teacon.jp
Open Graph description is not detected on the main page of Teacon. 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: