5.9 sec in total
101 ms
5.1 sec
717 ms
Click here to check amazing Locumpedia content. Otherwise, check out these important facts you probably never knew about locumpedia.com
Locumpedia is a free locum tenens industry platform that helps physicians, staffing firms & facilities make smart decisions. Register for free today.
Visit locumpedia.comWe analyzed Locumpedia.com page load time and found that the first response time was 101 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
locumpedia.com performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value3.5 s
64/100
25%
Value10.3 s
8/100
10%
Value3,330 ms
2/100
30%
Value0.476
18/100
15%
Value13.2 s
12/100
10%
101 ms
122 ms
376 ms
227 ms
31 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 78% of them (112 requests) were addressed to the original Locumpedia.com, 13% (18 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (482 ms) belongs to the original domain Locumpedia.com.
Page size can be reduced by 350.6 kB (31%)
1.1 MB
797.3 kB
In fact, the total size of Locumpedia.com main page is 1.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 533.7 kB which makes up the majority of the site volume.
Potential reduce by 339.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 339.0 kB or 86% of the original size.
Potential reduce by 25 B
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. Locumpedia images are well optimized though.
Potential reduce by 6.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 5.1 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. Locumpedia.com has all CSS files already compressed.
Number of requests can be reduced by 113 (97%)
117
4
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Locumpedia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 68 to 1 for JavaScripts and from 47 to 1 for CSS and as a result speed up the page load time.
locumpedia.com
101 ms
www.locumpedia.com
122 ms
www.locumpedia.com
376 ms
cyk0yww.css
227 ms
jquery.min.js
31 ms
jquery-migrate.min.js
25 ms
extension.min.js
159 ms
employer-id.js
159 ms
mark.js
224 ms
javascript;base64,alF1ZXJ5KGRvY3VtZW50KS5yZWFkeShmdW5jdGlvbigkKXt2YXIgZGVsYXk9MTAwO3NldFRpbWVvdXQoZnVuY3Rpb24oKXskKCcuZWxlbWVudG9yLXRhYi10aXRsZScpLnJlbW92ZUNsYXNzKCdlbGVtZW50b3ItYWN0aXZlJyk7JCgnLmVsZW1lbnRvci10YWItY29udGVudCcpLmNzcygnZGlzcGxheScsJ25vbmUnKX0sZGVsYXkpfSk=
1 ms
1089906bc8.js
229 ms
css
160 ms
autoptimize_single_c91819e2a398a839d51924247c579529.js
132 ms
autoptimize_single_2169afd7824e35ecc76d6207d7263a34.js
352 ms
gtm.js
267 ms
spai-lib-bg-compat.1.1.min.js
65 ms
bootstrap.min.js
54 ms
slick.min.js
55 ms
jquery.magnific-popup.min.js
54 ms
perfect-scrollbar.jquery.min.js
54 ms
waypoints.min.js
67 ms
sticky.min.js
70 ms
jquery.magnific-popup.min.js
63 ms
core.min.js
62 ms
mouse.min.js
89 ms
slider.min.js
94 ms
jquery.ui.touch-punch.min.js
95 ms
perfect-scrollbar.jquery.min.js
94 ms
prism-normalize-whitespace.min.js
96 ms
underscore.min.js
92 ms
jquery.mousewheel.min.js
95 ms
jquery.mCustomScrollbar.min.js
94 ms
select2.min.js
171 ms
imagesloaded.min.js
315 ms
jquery.magnific-popup.min.js
318 ms
isotope.min.js
314 ms
scripts.min.js
314 ms
swiper-bundle.min.js
477 ms
jquery.bxslider.min.js
482 ms
webpack-pro.runtime.min.js
356 ms
webpack.runtime.min.js
353 ms
frontend-modules.min.js
356 ms
wp-polyfill-inert.min.js
354 ms
regenerator-runtime.min.js
359 ms
wp-polyfill.min.js
361 ms
hooks.min.js
360 ms
i18n.min.js
373 ms
frontend.min.js
368 ms
frontend.min.js
374 ms
autoptimize_single_d0b8a1f4efabba1ab8e5b77e37e24603.css
368 ms
elements-handlers.min.js
440 ms
css
22 ms
autoptimize_single_b1ae68ba57619a4d63f41dd23155015d.js
425 ms
autoptimize_single_a406613b44910446ed2506e0417a1a62.js
425 ms
autoptimize_single_fb26890e6b4f799f0b34d42290c94c5a.js
428 ms
autoptimize_single_34c0807aacffe7112ad1780b0c5e8cad.js
427 ms
autoptimize_single_39a76744c533970d48d3fce99c72e92b.js
427 ms
autoptimize_single_b6b1205b2ace0b2d06e225c1d0945e95.js
427 ms
autoptimize_single_c84b9a8cb6e6696ed6d29b2e80270599.js
425 ms
autoptimize_single_f96b28fb164a59cfd4fa26c99b5dfec0.js
423 ms
autoptimize_single_babe736d7fec7c905c5617edadf4fbf4.js
422 ms
autoptimize_single_569cf59ed83f242eed77d9ad86d61925.js
420 ms
autoptimize_single_9b7bd1a4b016a96cc7f37eea32295d60.js
421 ms
autoptimize_single_386e649222d799bf02cf62232b4116e3.js
421 ms
css
30 ms
autoptimize_single_223a3b35ee0b0bee1d4111ef8ee90207.js
399 ms
autoptimize_single_f5dcd1b05f27a2889257a1270bfe1d5e.js
399 ms
autoptimize_single_c6f253fef8ea8b77d5157c43451c8577.js
400 ms
p.css
160 ms
autoptimize_single_1ebd2cf4a331806a1136a0b9a74ff2c0.js
397 ms
autoptimize_single_07b7b9c39583722586becacb83645d3c.js
396 ms
autoptimize_single_ed2a4da46568eb4080ede2396431343a.js
396 ms
autoptimize_single_5ecfc97f98f4182283767624aa556197.js
396 ms
autoptimize_single_890cc3c1dbfa7a6cf4ef53207b32d68c.js
398 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
149 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
200 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
222 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
224 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
223 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
222 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
221 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
221 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
224 ms
comphealth-logo-locumpedia.jpg
313 ms
autoptimize_single_0ace5afc7133f4d5a40eb209d963a01d.js
272 ms
autoptimize_single_416f52248a7f5b988d66f1ea80a196ce.js
278 ms
js
140 ms
analytics.js
120 ms
pxiGyp8kv8JHgFVrJJLucHtF.ttf
74 ms
pxiDyp8kv8JHgFVrJJLmg1hVF9eL.ttf
75 ms
pxiDyp8kv8JHgFVrJJLm21lVF9eL.ttf
109 ms
pxiDyp8kv8JHgFVrJJLmv1pVF9eL.ttf
113 ms
pxiAyp8kv8JHgFVrJJLmE0tCMPc.ttf
111 ms
pxiDyp8kv8JHgFVrJJLmr19VF9eL.ttf
113 ms
pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf
112 ms
pxiDyp8kv8JHgFVrJJLm111VF9eL.ttf
113 ms
pxiDyp8kv8JHgFVrJJLm81xVF9eL.ttf
114 ms
themify.woff
134 ms
fa-solid-900.woff
420 ms
fa-regular-400.woff
289 ms
collect
210 ms
autoptimize_single_cda8c3e9138f93dace6d22ccf468de50.css
165 ms
autoptimize_single_80fd67f3614ded0798aa4bba74b0532c.css
129 ms
autoptimize_single_b49e6b83f7bd47e2b24fae34688e415c.css
71 ms
extension.min.css
21 ms
font-awesome.min.css
23 ms
autoptimize_single_30b593b71d7672658f89bfea0ab360c9.css
18 ms
swiper-bundle.min.css
193 ms
autoptimize_single_0724b281e5177b9f50a32cf036ee5e3b.css
10 ms
fontawesome-webfont.woff
319 ms
autoptimize_single_75dd8da5c7c3d720ea9d20900e105bc6.css
11 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
1 ms
autoptimize_single_6b7939304e1bc55fac601aabffcc528d.css
30 ms
jquery.bxslider.min.css
217 ms
autoptimize_single_a3730a32c45428bf6874210a601c99f8.css
11 ms
autoptimize_single_4bdc66f5317b8df5269492a69cf61d57.css
217 ms
autoptimize_single_e6696bce03cc625efc95eb1fea652329.css
11 ms
autoptimize_single_4e8298094e3c736a92072f140b5cac38.css
36 ms
autoptimize_single_6a9f340cca2c6baa0699387c04621c9f.css
28 ms
pcp-likes-public.min.css
222 ms
autoptimize_single_7d861353d8ba16ee10d2425c0e56799f.css
20 ms
autoptimize_single_e45efcff8900148fd879a305103821ad.css
10 ms
magnific-popup.min.css
230 ms
autoptimize_single_618b09ad6e7615a54765de7495dcd58c.css
12 ms
autoptimize_single_2ee5d705a943a52ebc5bfea736a00565.css
11 ms
style.min.css
237 ms
autoptimize_single_dd3dcac06af9d4fca954cb1599700c49.css
18 ms
autoptimize_single_f38b2db10e01b1572732a3191d538707.css
11 ms
frontend-lite.min.css
20 ms
autoptimize_single_9fbb2ac9c38caea183ee010566a5c215.css
31 ms
autoptimize_single_bc1ca31e41a1eb97011bebad15a7f75f.css
25 ms
autoptimize_single_b1574524d2703f64b25cec2938ce1230.css
24 ms
autoptimize_single_ea197c11da0ce553cf8d4efc80707fd6.css
23 ms
swiper.min.css
23 ms
autoptimize_single_933108a9193b46e12df50dd6fec145b9.css
97 ms
autoptimize_single_d3852caa3ea7d26f8306b807fa7f4316.css
38 ms
frontend-lite.min.css
32 ms
autoptimize_single_4a9b533d15da8ddff558418f7569e7cb.css
86 ms
sliding-menu.min.css
38 ms
widget-icon-list.min.css
24 ms
widget-posts.min.css
31 ms
widget-icon-box.min.css
20 ms
select2.min.css
20 ms
animations.min.css
25 ms
locumpedia.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 input fields do not have accessible names
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
locumpedia.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
locumpedia.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locumpedia.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 Locumpedia.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.
locumpedia.com
Open Graph data is detected on the main page of Locumpedia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: