6.2 sec in total
1.1 sec
4.7 sec
450 ms
Visit ear.lk now to see the best up-to-date Ear content and also check out these interesting facts you probably never knew about ear.lk
Vision Care Hearing Solutions provide digital hearing aids in Sri Lanka at unbeatable prices. Learn more about these cutting-edge digitalhearing aids now!
Visit ear.lkWe analyzed Ear.lk page load time and found that the first response time was 1.1 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ear.lk performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value8.4 s
2/100
25%
Value11.8 s
4/100
10%
Value1,320 ms
17/100
30%
Value0.894
3/100
15%
Value17.2 s
4/100
10%
1053 ms
122 ms
182 ms
274 ms
378 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 72% of them (73 requests) were addressed to the original Ear.lk, 4% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ear.lk.
Page size can be reduced by 258.4 kB (12%)
2.2 MB
2.0 MB
In fact, the total size of Ear.lk main page is 2.2 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 62.4 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 13.7 kB, which is 18% 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 62.4 kB or 81% of the original size.
Potential reduce by 40.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. Ear images are well optimized though.
Potential reduce by 148.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 148.0 kB or 38% of the original size.
Potential reduce by 7.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.lk has all CSS files already compressed.
Number of requests can be reduced by 58 (64%)
90
32
The browser has sent 90 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 30 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.ear.lk
1053 ms
js
122 ms
wp-emoji-release.min.js
182 ms
styles.css
274 ms
style.css
378 ms
toolbar.css
397 ms
mu-style.css
373 ms
style.css
374 ms
dashicons.min.css
510 ms
bootstrap.css
384 ms
all.css
266 ms
aos.css
78 ms
lightgallery.css
478 ms
owl.carousel.min.css
479 ms
owl.theme.default.css
480 ms
flexslider.css
486 ms
hover.css
509 ms
style.css
684 ms
front-end.css
581 ms
frontend.css
589 ms
frontend-gtag.min.js
629 ms
jquery.js
749 ms
jquery-migrate.min.js
688 ms
sharethis.js
41 ms
sendpress.signup.js
689 ms
css
73 ms
scripts.js
636 ms
scripts.js
824 ms
element.js
119 ms
jquery.min.js
86 ms
bootstrap.js
825 ms
owl.carousel.min.js
825 ms
lightgallery-all.js
825 ms
jquery.flexslider.js
826 ms
aos.js
75 ms
jquery.form-validator.js
826 ms
assessment.js
825 ms
custom.js
862 ms
frontend.js
867 ms
hoverIntent.min.js
865 ms
maxmegamenu.js
871 ms
wp-embed.min.js
938 ms
christmas-snow.js
939 ms
jquery-ui.min.js
85 ms
snow-falling.js
957 ms
aos.css
103 ms
js
51 ms
js
107 ms
analytics.js
27 ms
aos.js
22 ms
collect
16 ms
snowfall-master.min.js
843 ms
collect
27 ms
ga-audiences
110 ms
css
12 ms
collect
103 ms
embed
203 ms
online-h.png
216 ms
book-a.png
232 ms
have-q.png
353 ms
logo.png
354 ms
res-menu.png
352 ms
rectangle.png
350 ms
Ear360-2.jpg
709 ms
av-pr1.png
352 ms
av-pr2.png
408 ms
Oticon_Opn_Park_Biking_ConnectClip_NDS_131030_Width200mm_300dpi_C_Oticon-min-e1536656430171.jpg
611 ms
welcm-right.png
509 ms
rectangle-back.png
427 ms
coma.png
426 ms
Testimony-nirmalan.jpg
513 ms
testimonial-desandu-1.jpg
546 ms
testimony-upali-1.jpg
546 ms
think-you.jpg
612 ms
btn-bg.png
718 ms
micp.png
667 ms
back-img.jpg
667 ms
BTE.png
741 ms
RITE-1.png
646 ms
CIC.png
950 ms
IIC.png
832 ms
ITC.png
736 ms
ITE-1.png
848 ms
logo.png
746 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf
30 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf
63 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf
78 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf
79 ms
AAABVuGyrgAA
14 ms
fa-brands-400.woff
118 ms
starkey-1.png
805 ms
Oticon.png
802 ms
ajax-loader.gif
805 ms
gb-mage.jpg
904 ms
e.png
898 ms
gABAAAABQCXAAMAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEABwAAAAEAAAAAAAIABwBgAAEAAAAAAAMABwA2AAEAAAAAAAQABwB1AAEAAAAAAAUACwAVAAEAAAAAAAYABwBLAAEAAAAAAAoAGgCKAAMAAQQJAAEADgAHAAMAAQQJAAIADgBnAAMAAQQJAAMADgA9AAMAAQQJAAQADgB8AAMAAQQJAAUAFgAgAAMAAQQJAAYADgBSAAMAAQQJAAoANACkaWNvbW9vbgBpAGMAbwBtAG8AbwBuVmVyc2lvbiAxLjAAVgBlAHIAcwBpAG8AbgAgADEALgAwaWNvbW9vbgBpAGMAbwBtAG8AbwBuaWNvbW9vbgBpAGMAbwBtAG8AbwBuUmVndWxhcgBSAGUAZwB1AGwAYQByaWNvbW9vbgBpAGMAbwBtAG8AbwBuRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
9 ms
js
161 ms
cd-top-arrow.svg
833 ms
1fa32b_5fe55a8e07c84f028c436637f9b7e6a6.png
821 ms
flags.png
685 ms
awr.png
780 ms
ear.lk 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.lk 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
Page has valid source maps
ear.lk 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ear.lk can be misinterpreted by Google and other search engines. Our service has detected that English 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 Ear.lk 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.lk
Open Graph data is detected on the main page of Ear. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: