1.3 sec in total
69 ms
943 ms
260 ms
Click here to check amazing Certify content for United States. Otherwise, check out these important facts you probably never knew about certify.com
Utilize our all-in-one expense tracking software to make expense reports a breeze. Get the plan that is right for you and never look back.
Visit certify.comWe analyzed Certify.com page load time and found that the first response time was 69 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
certify.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value10.1 s
0/100
25%
Value7.9 s
22/100
10%
Value1,860 ms
9/100
30%
Value0
100/100
15%
Value18.8 s
3/100
10%
69 ms
72 ms
67 ms
10 ms
8 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 54% of them (37 requests) were addressed to the original Certify.com, 12% (8 requests) were made to D1etmv6vmm5hjq.cloudfront.net and 6% (4 requests) were made to G2crowd.com. The less responsive or slowest element that took the longest time to load (392 ms) relates to the external source G2crowd.com.
Page size can be reduced by 206.9 kB (59%)
352.9 kB
146.0 kB
In fact, the total size of Certify.com main page is 352.9 kB. 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. Javascripts take 255.0 kB which makes up the majority of the site volume.
Potential reduce by 38.8 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 7.0 kB, which is 14% 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 38.8 kB or 77% of the original size.
Potential reduce by 1.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. Obviously, Certify needs image optimization as it can save up to 1.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 141.7 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 141.7 kB or 56% of the original size.
Potential reduce by 24.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. Certify.com needs all CSS files to be minified and compressed as it can save up to 24.5 kB or 78% of the original size.
Number of requests can be reduced by 18 (35%)
52
34
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Certify. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
certify.com
69 ms
www.certify.com
72 ms
css
67 ms
PublicStylesBundle92016102
10 ms
jquery-1.10.2.min.js
8 ms
PublicScriptsBundle92016102
33 ms
conversion.js
29 ms
MyIp.aspx
119 ms
grids.embed
392 ms
analytics.js
70 ms
collect
44 ms
59 ms
certify-logo-360x132.png
15 ms
certify-logo-notag.png
14 ms
iconShowMenu.png
16 ms
iconLogin.png
15 ms
VI_16af9480-fb4b-4a3a-ad47-cb4d57338caa_.aspx
60 ms
VI_9f4098e7-f2d3-4664-8606-eb8ec202a458_.aspx
58 ms
VI_f0d47b28-d275-43ea-9f81-6ae9b8f394fa_.aspx
58 ms
VI_7613c972-90c4-4954-ac78-bc792556424e_.aspx
58 ms
VI_af4c4349-861e-4d54-9261-434685acbc50_.aspx
58 ms
VI_2039d8e4-6a73-4f31-b56d-d00bad8b8e79_.aspx
58 ms
VI_35078868-5220-4146-ad3a-8e2d4ead5fcf_.aspx
116 ms
VI_a7e7c52c-11b6-466f-a95d-866af734c996_.aspx
117 ms
VI_4a0ffc6a-b3d3-40f9-b38a-7051d34a4f4b_.aspx
116 ms
VI_01fbb568-6067-4395-8b65-d9e8b0f884f0_.aspx
116 ms
VI_6003f616-1c80-4b63-b230-32e433c70c65_.aspx
114 ms
VI_e8b9be33-b34c-4c9e-87fa-f08813c1d6d3_.aspx
115 ms
VI_5b251c12-666d-4fd1-b84c-769827c293f3_.aspx
141 ms
VI_248adf5b-c105-42d6-90df-6c885686f78d_.aspx
142 ms
VI_c453e335-cf1f-4843-8b78-5eb138c2f4dd_.aspx
143 ms
VI_dbff4b34-d427-4cbe-84c0-fe3e65682b31_.aspx
144 ms
VI_3846a716-cf80-4bee-94fb-3f84159d007c_.aspx
141 ms
VI_f7274449-1a6c-4180-bbc4-30365a119ab2_.aspx
142 ms
VI_fa9743d9-4065-4ec2-97c4-0d61ce1ec1ee_.aspx
182 ms
VI_98ec30df-f566-4f5a-a8b2-e8b9b535da9c_.aspx
183 ms
VI_c34c66c8-7f90-4f0e-a05e-0feee708c933_.aspx
184 ms
star_checked.png
143 ms
VI_a50ddad0-1d88-4dce-a609-52fbecd91345_.aspx
185 ms
VI_faabb472-0bdc-494c-8b22-5b3be21f5e1c_.aspx
188 ms
VI_b893c69e-9a36-445d-82ed-e7110e07937a_.aspx
187 ms
VI_eae51d75-d7ef-46db-afcb-245647cad3b2_.aspx
219 ms
VI_9889d44f-dd94-4a11-9634-43d901843aea_.aspx
220 ms
icons_social_sprite.png
186 ms
collect
17 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
56 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
92 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
111 ms
M2Jd71oPJhLKp0zdtTvoM0DauxaEVho0aInXGvhmB4k.ttf
113 ms
29 ms
embedded_grid_assets-d30e559b66e051012e2c55e3a848f695.css
54 ms
sprites.css
29 ms
embedded_grid_assets-37559ad4cc4dd6dd7701725bea709a26.js
97 ms
mixpanel-2.2.min.js
162 ms
img.gif
31 ms
9k=
24 ms
CC53iJAAAAJXRFWHRkYXRlOmNyZWF0ZQAyMDE0LTExLTIwVDA5OjQzOjAzLTA2OjAwXsCDIwAAACV0RVh0ZGF0ZTptb2RpZnkAMjAxNC0xMS0yMFQwOTo0MzowMy0wNjowMC+dO58AAAAZdEVYdFNvZnR3YXJlAEFkb2JlIEltYWdlUmVhZHlxyWU8AAAAAElFTkSuQmCC
24 ms
xP+A0mCIOllQ6e6AAAAJXRFWHRkYXRlOmNyZWF0ZQAyMDE0LTA5LTIzVDA3OjIyOjU4LTA1OjAwvg1JrwAAACV0RVh0ZGF0ZTptb2RpZnkAMjAxNC0wOS0yM1QwNzoyMjo1OC0wNTowMM9Q8RMAAAAZdEVYdFNvZnR3YXJlAEFkb2JlIEltYWdlUmVhZHlxyWU8AAAAAElFTkSuQmCC
23 ms
2Q==
22 ms
g2-grid-7075fbec1390f2d49f969efaeddcf09e.png
121 ms
client_session.json
147 ms
analytics.js
145 ms
Urbano-Cond-webfont-dd8174dbcf29bc1eb6a867e4da1ba7fc.woff
24 ms
ProximaNova-Light-webfont-21c360802853f8d188c1b51f1ddb5ef9.woff
13 ms
ProximaNova-Thin-webfont-aa25b17ee62d2a09234a798290a81095.woff
38 ms
ProximaNova-Reg-webfont-7791e76b548c9cb13d8f4aa264a60837.woff
38 ms
ProximaNova-Sbold-webfont-3ebad95e9f9a0fb9ab4754564e8ce2be.woff
38 ms
33 ms
certify.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
Image elements do not have [alt] attributes
certify.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
certify.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Certify.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 Certify.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
certify.com
Open Graph description is not detected on the main page of Certify. 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: