3.6 sec in total
97 ms
3.3 sec
156 ms
Click here to check amazing Support Ezyvet content for United States. Otherwise, check out these important facts you probably never knew about support.ezyvet.com
Visit support.ezyvet.comWe analyzed Support.ezyvet.com page load time and found that the first response time was 97 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
support.ezyvet.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value6.5 s
9/100
25%
Value4.1 s
79/100
10%
Value350 ms
73/100
30%
Value0.402
25/100
15%
Value6.0 s
65/100
10%
97 ms
64 ms
62 ms
115 ms
47 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 11% of them (4 requests) were addressed to the original Support.ezyvet.com, 28% (10 requests) were made to Fonts.gstatic.com and 17% (6 requests) were made to D1hashle7dv0hm.cloudfront.net. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source S3.amazonaws.com.
Page size can be reduced by 795.3 kB (54%)
1.5 MB
679.7 kB
In fact, the total size of Support.ezyvet.com main page is 1.5 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. Javascripts take 959.7 kB which makes up the majority of the site volume.
Potential reduce by 13.5 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 3.5 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 13.5 kB or 62% of the original size.
Potential reduce by 14.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. Support Ezyvet images are well optimized though.
Potential reduce by 579.6 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 579.6 kB or 60% of the original size.
Potential reduce by 187.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. Support.ezyvet.com needs all CSS files to be minified and compressed as it can save up to 187.5 kB or 71% of the original size.
Number of requests can be reduced by 12 (52%)
23
11
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support Ezyvet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
support.ezyvet.com
97 ms
support.ezyvet.com
64 ms
home
62 ms
portal_utils-63b920a86a4acfe97c4d82c34c219ae6.css
115 ms
theme.css
47 ms
portal_head-d7fcffb338aa28a32fac29d147a655d3.js
128 ms
syntaxhighlighter-e8388ba351837cdd47f60739f85825f1.js
141 ms
portal_print-e7c8c1fc055b88c0b4d5591826cf1115.css
127 ms
portal_bottom-b4331e32cc32840ec096b50c83abd627.js
140 ms
redactor-45eaa568aae7da0b6422c35f70bd04c8.js
130 ms
freshfone_portal-63ff6c90a643b9fb016086d3f18e7943.js
124 ms
en-778a07cfd489027db5c7ac2a4523553f.js
123 ms
css
98 ms
ezyvet_logo-360x100.png
2906 ms
createTicket.png
242 ms
freshdeskbg.png
270 ms
ezyvet_logo-360x100.png
137 ms
checkTicket.png
174 ms
search.png
183 ms
knowledgeIcon.png
173 ms
announcements_home.png
182 ms
communityIcon.png
182 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
178 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
193 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
218 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
219 ms
4cKlrioa77J2iqTqBgkRWg.ttf
220 ms
LqowQDslGv4DmUBAfWa2Vw.ttf
219 ms
2HG_tEPiQ4Z6795cGfdivKCWcynf_cDxXwCLxiixG1c.ttf
217 ms
gc5ZVKiLNkRdGlU3GaSVBfesZW2xOQ-xsNqO47m55DA.ttf
220 ms
HkF_qI1x_noxlxhrhMQYEKCWcynf_cDxXwCLxiixG1c.ttf
220 ms
VNUH7ZAcagYBWsAiBBCEY6CWcynf_cDxXwCLxiixG1c.ttf
220 ms
visitor.css
157 ms
visitor.js
177 ms
0
39 ms
teamstatus
466 ms
support.ezyvet.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.
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
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.
support.ezyvet.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
support.ezyvet.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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.ezyvet.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 Support.ezyvet.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.
support.ezyvet.com
Open Graph description is not detected on the main page of Support Ezyvet. 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: