2.4 sec in total
176 ms
2 sec
212 ms
Welcome to odgers.com homepage info - get ready to check Odgers best content right away, or after learning these important things about odgers.com
Board & divisional board level executive recruitment solutions for American & international clients.
Visit odgers.comWe analyzed Odgers.com page load time and found that the first response time was 176 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
odgers.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value9.7 s
0/100
25%
Value8.7 s
16/100
10%
Value930 ms
30/100
30%
Value0.032
100/100
15%
Value13.2 s
12/100
10%
176 ms
168 ms
243 ms
246 ms
555 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Odgers.com, 89% (33 requests) were made to Odgersberndtson.co.uk and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Odgersberndtson.co.uk.
Page size can be reduced by 325.4 kB (66%)
492.8 kB
167.3 kB
In fact, the total size of Odgers.com main page is 492.8 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. 15% of websites need less resources to load. Javascripts take 297.3 kB which makes up the majority of the site volume.
Potential reduce by 41.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. 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 41.4 kB or 81% of the original size.
Potential reduce by 5.1 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. Odgers images are well optimized though.
Potential reduce by 201.8 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 201.8 kB or 68% of the original size.
Potential reduce by 77.2 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. Odgers.com needs all CSS files to be minified and compressed as it can save up to 77.2 kB or 82% of the original size.
Number of requests can be reduced by 13 (38%)
34
21
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Odgers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
odgers.com
176 ms
www.odgersberndtson.co.uk
168 ms
243 ms
merged-d06b7bf6d5264a75d511e6a962bce496-a55b2523e751c37db5bbff8021bd1dd8.css
246 ms
merged-cf6676ccb5a23e6e610b9e2ee665afe5-2cfc768b91a114b0819792b4f0c9ce5c.js
555 ms
analytics.js
36 ms
arrow_down.png
160 ms
mag.png
161 ms
gb.gif
163 ms
header_bg.gif
162 ms
logo_en.gif
168 ms
logo_print.png
316 ms
bnr-home-oct2015-update.jpg
557 ms
button_arrow.gif
318 ms
icon_eye_11.gif
324 ms
icon_people_04.gif
326 ms
icon_clipboard_05.gif
437 ms
icon_binocular_03.gif
473 ms
uk_map.jpg
475 ms
twitter.png
480 ms
facebook.png
482 ms
linkedin.png
590 ms
logo_interim_01.gif
626 ms
logo_berwick.gif
632 ms
slideshow_shadow.png
618 ms
arrow.gif
627 ms
icon_enquiry.gif
693 ms
line.gif
727 ms
icon_submit.gif
770 ms
icon_head.gif
771 ms
footer_bg.gif
778 ms
bullet_arrow_footer.gif
791 ms
footer_divider.gif
846 ms
Lorimer_Medium-webfont.woff
1042 ms
collect
2 ms
collect
51 ms
merged-2395000e1134f2b065d7200dfbe595a5-f1118d943fac369bfab8c26dea1f312a.css
80 ms
odgers.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
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.
odgers.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
odgers.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
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 Odgers.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 Odgers.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.
odgers.com
Open Graph description is not detected on the main page of Odgers. 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: