15.8 sec in total
4.5 sec
11 sec
252 ms
Visit easmed.com now to see the best up-to-date Easmed content and also check out these interesting facts you probably never knew about easmed.com
Easmed is a leading distributor specialising in the fields of ENT and Sleep Medicine in South-East Asia
Visit easmed.comWe analyzed Easmed.com page load time and found that the first response time was 4.5 sec and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
easmed.com performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value28.6 s
0/100
25%
Value18.8 s
0/100
10%
Value320 ms
76/100
30%
Value0.017
100/100
15%
Value17.2 s
4/100
10%
4516 ms
1388 ms
692 ms
464 ms
694 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 93% of them (63 requests) were addressed to the original Easmed.com, 4% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Easmed.com.
Page size can be reduced by 993.6 kB (44%)
2.3 MB
1.3 MB
In fact, the total size of Easmed.com main page is 2.3 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. Images take 985.5 kB which makes up the majority of the site volume.
Potential reduce by 30.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. 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 30.1 kB or 82% of the original size.
Potential reduce by 17.2 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. Easmed images are well optimized though.
Potential reduce by 638.2 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 638.2 kB or 71% of the original size.
Potential reduce by 308.0 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. Easmed.com needs all CSS files to be minified and compressed as it can save up to 308.0 kB or 86% of the original size.
Number of requests can be reduced by 47 (77%)
61
14
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Easmed. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.easmed.com
4516 ms
style.css
1388 ms
layerslider.css
692 ms
skin.css
464 ms
font-awesome.css
694 ms
owl.carousel.css
466 ms
jquery.fancybox.css
478 ms
color-cyan.css
925 ms
styles.css
694 ms
wprmenu.css
707 ms
css
14 ms
style.css
1616 ms
jquery.fancybox-1.3.7.min.css
695 ms
jquery.js
1628 ms
jquery-migrate.min.js
712 ms
jquery.transit.min.js
926 ms
jquery.sidr.js
927 ms
wprmenu.js
943 ms
jquery.min.js
1624 ms
jquery-ui.min.js
1386 ms
jquery.migrate.min.js
1176 ms
owl.carousel.min.js
1383 ms
jquery.isotope.min.js
1403 ms
jquery.fancybox.pack.js
1621 ms
jquery.fancybox-media.js
1622 ms
jquery.flot.js
2326 ms
jquery.flot.pie.js
1840 ms
jquery.flot.categories.js
1844 ms
greensock.js
2074 ms
layerslider.transitions.js
1845 ms
layerslider.kreaturamedia.jquery.js
2076 ms
jquery.superscrollorama.js
2069 ms
TweenMax.min.js
2304 ms
TimelineMax.min.js
2075 ms
jquery.ui.core.min.js
2299 ms
jquery.ui.widget.min.js
2303 ms
jquery.ui.tabs.min.js
2305 ms
jquery-ui-tabs-rotate.js
2300 ms
jquery.ui.accordion.min.js
2306 ms
jquery.tweet.js
2308 ms
jquery.easypiechart.js
2296 ms
jquery.autocomplete.min.js
2085 ms
scripts.js
2084 ms
jquery.form.min.js
2099 ms
scripts.js
2291 ms
jquery.fancybox-1.3.7.min.js
2082 ms
jquery.easing.pack.js
2083 ms
jquery.mousewheel.min.js
2068 ms
wp-emoji-release.min.js
1691 ms
header.png
2104 ms
logo.png
1353 ms
medical-slide-1.jpg
2050 ms
medical-slide-2.jpg
2050 ms
medical-slide-3.jpg
2514 ms
photo-tour-6.jpg
1361 ms
Patient.jpg
1583 ms
our-phylosophy.jpg
1594 ms
client.jpg
1814 ms
client2.jpg
1825 ms
2190746.js
34 ms
skin.css
1562 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
25 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
25 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
26 ms
fancybox_sprite.png
235 ms
blank.gif
1144 ms
skin.png
236 ms
fontawesome-webfont-v=4.0.3.svg
925 ms
easmed.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
easmed.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
Issues were logged in the Issues panel in Chrome Devtools
easmed.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Easmed.com 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 Easmed.com 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.
easmed.com
Open Graph description is not detected on the main page of Easmed. 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: