9.8 sec in total
2.3 sec
7.3 sec
194 ms
Welcome to ear.com.tw homepage info - get ready to check Ear best content for Taiwan right away, or after learning these important things about ear.com.tw
全台灣最大連鎖品牌科林助聽器 | 服務據點最多通過SGS ISO國際認證助聽器公司 | 免費聽力檢測、助聽器選配、試聽試戴、人工電子耳諮詢、oticon奧迪康助聽器獨家代理。致力全體華人聽力保健服務。提供2023最新助聽器補助資訊與助聽器代償墊付。
Visit ear.com.twWe analyzed Ear.com.tw page load time and found that the first response time was 2.3 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ear.com.tw performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value11.8 s
0/100
25%
Value10.4 s
8/100
10%
Value720 ms
41/100
30%
Value0
100/100
15%
Value14.5 s
8/100
10%
2318 ms
1493 ms
420 ms
626 ms
839 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 45% of them (60 requests) were addressed to the original Ear.com.tw, 18% (24 requests) were made to Static.xx.fbcdn.net and 15% (20 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Ear.com.tw.
Page size can be reduced by 607.7 kB (39%)
1.6 MB
944.4 kB
In fact, the total size of Ear.com.tw main page is 1.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 952.6 kB which makes up the majority of the site volume.
Potential reduce by 86.2 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 16.3 kB, which is 16% 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 86.2 kB or 83% of the original size.
Potential reduce by 174.0 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. Obviously, Ear needs image optimization as it can save up to 174.0 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 233.3 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 233.3 kB or 64% of the original size.
Potential reduce by 114.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. Ear.com.tw needs all CSS files to be minified and compressed as it can save up to 114.3 kB or 88% of the original size.
Number of requests can be reduced by 45 (35%)
128
83
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
ear.com.tw
2318 ms
fin.css
1493 ms
clinico.css
420 ms
AC_RunActiveContent.js
626 ms
swfobject.js
839 ms
script.js
627 ms
menu.css
424 ms
jquery-1.7.1.min.js
1501 ms
jquery.prettyPhoto.js
1050 ms
custom.js
841 ms
prettyPhoto.css
1055 ms
cinico.js
868 ms
clinico_plugins.js
1051 ms
sprout-slide.css
1076 ms
kf.asp
682 ms
jquery.toggleElements.pack.js
637 ms
langConvert.js
810 ms
conversion.js
33 ms
cinicoindex.js
609 ms
sprout-slide.js
630 ms
jquery.touchSwipe.js
1228 ms
reset.css
209 ms
analytics.js
43 ms
ytc.js
60 ms
bat.js
192 ms
hm.js
1364 ms
top_bg.png
245 ms
logo.png
239 ms
f_ad1458028347.jpg
3344 ms
f_ad1438760420.jpg
3307 ms
f_ad1457327908.jpg
1693 ms
f_ad1438760648.jpg
890 ms
f_ad1446011611.jpg
3528 ms
f_ad1440580031.jpg
816 ms
arrow_1.gif
1190 ms
in_tt_fb2.gif
1190 ms
A+.jpg
1376 ms
top_mail.gif
1372 ms
sitemap.gif
1579 ms
top_branches.gif
1583 ms
search_box.gif
1787 ms
btn_search.gif
1792 ms
brick_bk.png
1885 ms
brick_case_bk.gif
1989 ms
prev_next.gif
1993 ms
sidebar_hr.gif
2094 ms
in_tt_news2.gif
2197 ms
sdk.js
20 ms
collect
31 ms
widget_v2.134.js
31 ms
128 ms
collect
158 ms
222 ms
xd_arbiter.php
34 ms
xd_arbiter.php
74 ms
71 ms
api.php
2535 ms
api.php
2522 ms
footer_map.gif
1813 ms
prev.png
1910 ms
next.png
2014 ms
__$$__stringtable_lang_zh_TW.js
16 ms
page.php
339 ms
avatar_simple_visitor.png
81 ms
eU1V78KtO5T.css
49 ms
O00-EUb8umQ.css
52 ms
haVjXmh8926.css
53 ms
AjtbmHfZ9M5.css
60 ms
4IatoeaEfSb.css
57 ms
q68gy-v_YMF.js
62 ms
k19Xse48j5I.js
83 ms
ihptErjAmMX.js
83 ms
3So47A9WcrL.js
79 ms
cUsKAwzqrQw.js
98 ms
vErY8zngADX.js
111 ms
6PDLJFN-l6_.js
80 ms
FzGTmhgBEqv.js
125 ms
lRyN50VcaFW.js
128 ms
aL63HcygAAVYuCCsAAA==
1 ms
11813537_488046938041854_7433977296339065261_n.jpg
233 ms
safe_image.php
305 ms
b8XhdWI9eAN.js
91 ms
safe_image.php
82 ms
safe_image.php
84 ms
11831790_488039128042635_7590351048069874439_n.jpg
72 ms
10377177_564961660350381_6122373563115650530_n.jpg
72 ms
12063502_564962623683618_4206474782492098649_n.jpg
79 ms
12672522_564422073737673_1929241314_n.jpg
79 ms
wL6VQj7Ab77.png
61 ms
s7jcwEQH7Sx.png
57 ms
GtIpNnEyqq_.png
58 ms
e3Spc1mcUJw.png
70 ms
1BQnIVjTFoC.js
23 ms
R9a_DtVRZgv.js
10 ms
cUDgRFxaoIk.js
11 ms
0JBr1QHp8Gi.js
11 ms
kDOzhTr2W91.js
12 ms
hm.gif
1136 ms
mqdefault.jpg
46 ms
type2_oticon_alta_pro_s.png
216 ms
type1_oticon_chili_s.png
219 ms
type2_bernafon_carista_s.png
631 ms
type2_oticon_acto_pro_s.png
431 ms
type1_bernafon_carista_s.png
432 ms
type1_oticon_acto_pro_s.png
758 ms
type3_oticon_nera_s.png
795 ms
type1_bernafon_inizia_s.png
642 ms
type1_bernafon_chronos_s.png
645 ms
type2_oticon_nera_s.png
1185 ms
type1_oticon_nera_s.png
1047 ms
type1_oticon_safari_s.png
854 ms
in_case_pro.png
856 ms
btn_friend.png
969 ms
mqdefault.jpg
17 ms
mqdefault.jpg
19 ms
mqdefault.jpg
16 ms
mqdefault.jpg
15 ms
mqdefault.jpg
34 ms
mqdefault.jpg
15 ms
mqdefault.jpg
35 ms
mqdefault.jpg
33 ms
mqdefault.jpg
32 ms
mqdefault.jpg
33 ms
mqdefault.jpg
33 ms
mqdefault.jpg
46 ms
mqdefault.jpg
49 ms
mqdefault.jpg
47 ms
mqdefault.jpg
51 ms
mqdefault.jpg
55 ms
mqdefault.jpg
64 ms
mqdefault.jpg
59 ms
mqdefault.jpg
62 ms
ear.com.tw 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 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.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
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>).
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.
ear.com.tw 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
ear.com.tw 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
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ear.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Ear.com.tw 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.
ear.com.tw
Open Graph description is not detected on the main page of Ear. 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: