4.1 sec in total
303 ms
3.4 sec
440 ms
Visit equimed.com now to see the best up-to-date Equi Med content for United States and also check out these interesting facts you probably never knew about equimed.com
Horse health information.
Visit equimed.comWe analyzed Equimed.com page load time and found that the first response time was 303 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
equimed.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value6.1 s
12/100
25%
Value3.9 s
82/100
10%
Value630 ms
47/100
30%
Value0.001
100/100
15%
Value8.8 s
36/100
10%
303 ms
3 ms
124 ms
125 ms
127 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 9% of them (10 requests) were addressed to the original Equimed.com, 20% (23 requests) were made to Equimed-static.com and 13% (15 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Equimed-static.com.
Page size can be reduced by 739.7 kB (39%)
1.9 MB
1.2 MB
In fact, the total size of Equimed.com main page is 1.9 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 849.5 kB which makes up the majority of the site volume.
Potential reduce by 129.0 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 129.0 kB or 81% of the original size.
Potential reduce by 7.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. Equi Med images are well optimized though.
Potential reduce by 419.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 419.3 kB or 62% of the original size.
Potential reduce by 183.5 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. Equimed.com needs all CSS files to be minified and compressed as it can save up to 183.5 kB or 79% of the original size.
Number of requests can be reduced by 54 (49%)
111
57
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Equi Med. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
equimed.com
303 ms
jquery-ui.css
3 ms
css_dCl1AAJlqnF2P1L4NPcwD27p0aNMaA2Qy4EPvsxQkUA.css
124 ms
css_o8zGWFjzm5V2bmTJCf6i0R9cei-STfkhNmsmEETRlR0.css
125 ms
css_Wu8npAzy16WmnnnWKxpexfgsAryolGGaX6yO3GWA5bU.css
127 ms
css_kqsGGiEtmOK9aGRc5-4ZsYhuwz8MilHfv-5coRaiSdA.css
185 ms
js_1wQzuzAe24n2dnkmuyobl8nRdOldGAxnkM-bkq6dyrM.js
191 ms
js_DHI0yJPzxnOQI0Sl_DRG2IV2mf-4XCccEj0OhEIKsWk.js
179 ms
widgets.js
5 ms
header-bg.jpg
186 ms
ga.js
74 ms
2sr.png
166 ms
76102450
115 ms
ir
45 ms
4c.png
126 ms
201.png
126 ms
3wh.jpg
314 ms
3wj.jpg
266 ms
2iv.jpg
1149 ms
2iu.jpg
250 ms
2it.jpg
251 ms
2m8.png
364 ms
2il.png
312 ms
2jr.png
311 ms
26q.jpg
326 ms
49u.jpg
672 ms
499.jpg
373 ms
1yb.jpg
371 ms
228.jpg
386 ms
27k.jpg
423 ms
28o.jpg
432 ms
3yt.jpg
614 ms
pixel.gif
446 ms
3wn.gif
483 ms
Museo_Slab_500-webfont.woff
144 ms
2a1.png
483 ms
__utm.gif
31 ms
51XiHcQbHdL._SL160_.jpg
15 ms
ajs.php
1118 ms
player.js
97 ms
player.css
70 ms
ga.js
93 ms
vuid.min.js
95 ms
__utm.gif
74 ms
proxy.html
41 ms
521263094.webp
75 ms
3wf.jpg
246 ms
lg.php
68 ms
ui-bg_highlight-soft_100_ffffff_1x100.png
63 ms
ajs.php
120 ms
adsbygoogle.js
7 ms
ag.php
64 ms
lg.php
925 ms
ca-pub-8126779091551045.js
54 ms
zrt_lookup.html
39 ms
show_ads_impl.js
60 ms
ajs.php
66 ms
ads
218 ms
osd.js
5 ms
ir
17 ms
lg.php
66 ms
ajs.php
738 ms
m_js_controller.js
22 ms
abg.js
41 ms
favicon
62 ms
googlelogo_color_112x36dp.png
47 ms
nessie_icon_thin_arrow_big_white.png
23 ms
s
17 ms
x_button_blue2.png
6 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
3 ms
a90279db5011e609bdfc7d3fd0ba7a0b.png
128 ms
lg.php
79 ms
all.js
45 ms
plusone.js
127 ms
pinit.js
31 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
40 ms
208 ms
xd_arbiter.php
26 ms
xd_arbiter.php
109 ms
pinit_main.js
42 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
27 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
69 ms
info.json
172 ms
cb=gapi.loaded_0
52 ms
cb=gapi.loaded_1
73 ms
fastbutton
127 ms
fastbutton
124 ms
fastbutton
141 ms
fastbutton
121 ms
fastbutton
130 ms
fastbutton
200 ms
fastbutton
198 ms
fastbutton
207 ms
postmessageRelay
45 ms
rs=AGLTcCPNzfuyiR2SRdOysTpopVYTZZwedQ
28 ms
api.js
100 ms
core:rpc:shindig.random:shindig.sha1.js
129 ms
2536007149-postmessagerelay.js
101 ms
cb=gapi.loaded_0
73 ms
cb=gapi.loaded_1
60 ms
grlryt2bdKIyfMSOhzd1eA.woff
165 ms
ui
30 ms
xd_arbiter.php
8 ms
like.php
58 ms
like.php
91 ms
like.php
84 ms
like.php
97 ms
like.php
107 ms
like.php
100 ms
like.php
110 ms
like.php
116 ms
vpc6VNjRPXV.js
32 ms
LVx-xkvaJ0b.png
32 ms
like.php
104 ms
jot.html
2 ms
equimed.com 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
equimed.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
Browser errors were logged to the console
Page has valid source maps
equimed.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Equimed.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Equimed.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.
equimed.com
Open Graph description is not detected on the main page of Equi Med. 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: