6.7 sec in total
117 ms
6 sec
667 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 117 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
locumpedia.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value7.0 s
6/100
25%
Value7.5 s
27/100
10%
Value1,110 ms
23/100
30%
Value0.533
14/100
15%
Value13.0 s
13/100
10%
117 ms
99 ms
70 ms
34 ms
90 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 45% of them (67 requests) were addressed to the original Locumpedia.com, 36% (54 requests) were made to Sp-ao.shortpixel.ai and 12% (18 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (572 ms) relates to the external source Sp-ao.shortpixel.ai.
Page size can be reduced by 353.1 kB (43%)
820.7 kB
467.5 kB
In fact, the total size of Locumpedia.com main page is 820.7 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. 75% 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. HTML takes 407.1 kB which makes up the majority of the site volume.
Potential reduce by 348.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. 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 348.5 kB or 86% of the original size.
Potential reduce by 0 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 2.1 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 2.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. Locumpedia.com has all CSS files already compressed.
Number of requests can be reduced by 115 (97%)
118
3
The browser has sent 118 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 61 to 1 for JavaScripts and from 56 to 1 for CSS and as a result speed up the page load time.
locumpedia.com
117 ms
www.locumpedia.com
99 ms
www.locumpedia.com
70 ms
jquery.min.js
34 ms
jquery-migrate.min.js
90 ms
extension.min.js
107 ms
autoptimize_single_c91819e2a398a839d51924247c579529.js
251 ms
employer-id.js
106 ms
mark.js
123 ms
css
124 ms
cyk0yww.css
236 ms
autoptimize_single_2169afd7824e35ecc76d6207d7263a34.js
254 ms
javascript;base64,alF1ZXJ5KGRvY3VtZW50KS5yZWFkeShmdW5jdGlvbigkKXt2YXIgZGVsYXk9MTAwO3NldFRpbWVvdXQoZnVuY3Rpb24oKXskKCcuZWxlbWVudG9yLXRhYi10aXRsZScpLnJlbW92ZUNsYXNzKCdlbGVtZW50b3ItYWN0aXZlJyk7JCgnLmVsZW1lbnRvci10YWItY29udGVudCcpLmNzcygnZGlzcGxheScsJ25vbmUnKX0sZGVsYXkpfSk=
9 ms
1089906bc8.js
169 ms
autoptimize_single_b1ae68ba57619a4d63f41dd23155015d.js
233 ms
bootstrap.min.js
103 ms
slick.min.js
102 ms
jquery.magnific-popup.min.js
116 ms
autoptimize_single_a406613b44910446ed2506e0417a1a62.js
232 ms
perfect-scrollbar.jquery.min.js
121 ms
autoptimize_single_0ace5afc7133f4d5a40eb209d963a01d.js
232 ms
autoptimize_single_fb26890e6b4f799f0b34d42290c94c5a.js
232 ms
autoptimize_single_66c003f9065724f5b605c3efe4380f1b.js
347 ms
autoptimize_single_39a76744c533970d48d3fce99c72e92b.js
372 ms
jquery.magnific-popup.min.js
118 ms
core.min.js
134 ms
mouse.min.js
134 ms
slider.min.js
115 ms
jquery.ui.touch-punch.min.js
135 ms
autoptimize_single_b6b1205b2ace0b2d06e225c1d0945e95.js
351 ms
autoptimize_single_416f52248a7f5b988d66f1ea80a196ce.js
346 ms
perfect-scrollbar.jquery.min.js
136 ms
autoptimize_single_f96b28fb164a59cfd4fa26c99b5dfec0.js
377 ms
autoptimize_single_c84b9a8cb6e6696ed6d29b2e80270599.js
351 ms
prism-normalize-whitespace.min.js
134 ms
autoptimize_single_babe736d7fec7c905c5617edadf4fbf4.js
393 ms
autoptimize_single_569cf59ed83f242eed77d9ad86d61925.js
394 ms
autoptimize_single_386e649222d799bf02cf62232b4116e3.js
421 ms
autoptimize_single_9b7bd1a4b016a96cc7f37eea32295d60.js
480 ms
autoptimize_single_223a3b35ee0b0bee1d4111ef8ee90207.js
538 ms
autoptimize_single_1ebd2cf4a331806a1136a0b9a74ff2c0.js
444 ms
autoptimize_single_f5dcd1b05f27a2889257a1270bfe1d5e.js
480 ms
autoptimize_single_c6f253fef8ea8b77d5157c43451c8577.js
479 ms
imagesloaded.min.js
152 ms
autoptimize_single_ed2a4da46568eb4080ede2396431343a.js
530 ms
underscore.min.js
133 ms
autoptimize_single_5ecfc97f98f4182283767624aa556197.js
555 ms
jquery.mousewheel.min.js
135 ms
jquery.mCustomScrollbar.min.js
152 ms
autoptimize_single_07b7b9c39583722586becacb83645d3c.js
558 ms
select2.min.js
162 ms
jquery.magnific-popup.min.js
152 ms
isotope.min.js
153 ms
scripts.min.js
153 ms
swiper-bundle.min.js
192 ms
jquery.bxslider.min.js
161 ms
autoptimize_single_d95beb0a21cea323311c7bfd35bed9f9.js
572 ms
webpack-pro.runtime.min.js
161 ms
webpack.runtime.min.js
173 ms
frontend-modules.min.js
175 ms
hooks.min.js
191 ms
i18n.min.js
192 ms
frontend.min.js
175 ms
frontend.min.js
190 ms
elements-handlers.min.js
227 ms
gtm.js
125 ms
spai-lib-bg-compat.1.1.min.js
412 ms
comphealth-logo-locumpedia.jpg
505 ms
css
16 ms
css
40 ms
pxiEyp8kv8JHgFVrJJfed3FHGPc.ttf
40 ms
pxiByp8kv8JHgFVrLGT9Z1xlEN2JQEk.ttf
59 ms
pxiByp8kv8JHgFVrLDz8Z1xlEN2JQEk.ttf
75 ms
pxiByp8kv8JHgFVrLFj_Z1xlEN2JQEk.ttf
75 ms
pxiGyp8kv8JHgFVrLPTucHtFOvWDSA.ttf
92 ms
pxiByp8kv8JHgFVrLEj6Z1xlEN2JQEk.ttf
92 ms
pxiByp8kv8JHgFVrLCz7Z1xlEN2JQEk.ttf
91 ms
pxiByp8kv8JHgFVrLDD4Z1xlEN2JQEk.ttf
91 ms
pxiByp8kv8JHgFVrLBT5Z1xlEN2JQEk.ttf
92 ms
p.css
73 ms
extension.min.css
71 ms
themify.woff
48 ms
pxiGyp8kv8JHgFVrJJLucHtFOvWDSA.ttf
44 ms
pxiDyp8kv8JHgFVrJJLmg1hVF9eLYktMqg.ttf
47 ms
pxiDyp8kv8JHgFVrJJLm21lVF9eLYktMqg.ttf
44 ms
pxiDyp8kv8JHgFVrJJLmv1pVF9eLYktMqg.ttf
44 ms
pxiAyp8kv8JHgFVrJJLmE0tCMPehSkFE.ttf
44 ms
pxiDyp8kv8JHgFVrJJLmr19VF9eLYktMqg.ttf
47 ms
pxiDyp8kv8JHgFVrJJLmy15VF9eLYktMqg.ttf
46 ms
pxiDyp8kv8JHgFVrJJLm111VF9eLYktMqg.ttf
48 ms
pxiDyp8kv8JHgFVrJJLm81xVF9eLYktMqg.ttf
48 ms
fa-solid-900.woff
48 ms
fa-regular-400.woff
74 ms
font-awesome.min.css
23 ms
swiper-bundle.min.css
25 ms
fontawesome-webfont.woff
252 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
2 ms
autoptimize_single_f9b5596e5b76e57544feb48e13758122.css
153 ms
jquery.bxslider.min.css
29 ms
pcp-likes-public.min.css
17 ms
magnific-popup.min.css
42 ms
autoptimize_single_7f8a49cd964dda6256e44289d561a2bd.css
137 ms
fontello.min.css
19 ms
style.min.css
21 ms
fontello.woff
211 ms
autoptimize_single_80fd67f3614ded0798aa4bba74b0532c.css
120 ms
autoptimize_single_30b593b71d7672658f89bfea0ab360c9.css
132 ms
tribe-events-single-skeleton.min.css
18 ms
tribe-events-single-full.min.css
22 ms
widget-base.min.css
86 ms
autoptimize_single_0724b281e5177b9f50a32cf036ee5e3b.css
136 ms
frontend.min.css
20 ms
widget-image.min.css
20 ms
widget-icon-box.min.css
84 ms
autoptimize_single_75dd8da5c7c3d720ea9d20900e105bc6.css
150 ms
fadeIn.min.css
17 ms
swiper.min.css
16 ms
e-swiper.min.css
68 ms
autoptimize_single_6b7939304e1bc55fac601aabffcc528d.css
124 ms
popup.min.css
14 ms
widget-heading.min.css
57 ms
autoptimize_single_e2924b2eddbeea56afeed1258ef30000.css
145 ms
widget-posts.min.css
19 ms
widget-image-box.min.css
16 ms
widget-text-editor.min.css
44 ms
autoptimize_single_eb75fddcb677591a18b8497a0212bac1.css
167 ms
sliding-menu.min.css
22 ms
widget-icon-list.min.css
16 ms
select2.min.css
91 ms
autoptimize_single_7ca91210d923d0fe6fdc061d70018aa6.css
127 ms
widget-divider.min.css
21 ms
autoptimize_single_4e8298094e3c736a92072f140b5cac38.css
134 ms
autoptimize_single_6a9f340cca2c6baa0699387c04621c9f.css
135 ms
autoptimize_single_7d861353d8ba16ee10d2425c0e56799f.css
183 ms
autoptimize_single_e45efcff8900148fd879a305103821ad.css
117 ms
fa-solid-900.woff
4 ms
fa-regular-400.woff
164 ms
autoptimize_single_618b09ad6e7615a54765de7495dcd58c.css
152 ms
autoptimize_single_2ee5d705a943a52ebc5bfea736a00565.css
91 ms
themify.woff
3 ms
autoptimize_single_dd3dcac06af9d4fca954cb1599700c49.css
131 ms
autoptimize_single_f38b2db10e01b1572732a3191d538707.css
127 ms
autoptimize_single_9fbb2ac9c38caea183ee010566a5c215.css
177 ms
autoptimize_single_bc1ca31e41a1eb97011bebad15a7f75f.css
146 ms
autoptimize_single_b1574524d2703f64b25cec2938ce1230.css
134 ms
autoptimize_single_2e8dc6645307b09a2891b637b04e346c.css
139 ms
autoptimize_single_5ea2e1f534cecf8681be866d9e095308.css
171 ms
autoptimize_single_82689f5bd38b931d6c22656e10098f2a.css
124 ms
autoptimize_single_319f8ca825fae21feb5b2ebe14a3183f.css
123 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: