3.4 sec in total
200 ms
2.1 sec
1.1 sec
Welcome to docline.es homepage info - get ready to check Docline best content for Spain right away, or after learning these important things about docline.es
La plataforma de telemedicina más completa del mercado para empresas, hospitales y profesionales de la salud.
Visit docline.esWe analyzed Docline.es page load time and found that the first response time was 200 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
docline.es performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value9.3 s
1/100
25%
Value6.7 s
37/100
10%
Value0 ms
100/100
30%
Value0.553
13/100
15%
Value3.6 s
91/100
10%
200 ms
20 ms
40 ms
30 ms
22 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Docline.es, 3% (3 requests) were made to Beacon-v2.helpscout.net and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (655 ms) relates to the external source Docline.com.
Page size can be reduced by 540.5 kB (38%)
1.4 MB
878.1 kB
In fact, the total size of Docline.es main page is 1.4 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. 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. Javascripts take 496.5 kB which makes up the majority of the site volume.
Potential reduce by 346.3 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 346.3 kB or 86% of the original size.
Potential reduce by 44 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. Docline images are well optimized though.
Potential reduce by 128.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 128.6 kB or 26% of the original size.
Potential reduce by 65.6 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. Docline.es needs all CSS files to be minified and compressed as it can save up to 65.6 kB or 33% of the original size.
Number of requests can be reduced by 51 (61%)
84
33
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.docline.com
200 ms
uc.js
20 ms
style.min.css
40 ms
common.css
30 ms
bootstrap.min.css
22 ms
custom-frontend.min.css
359 ms
custom-pro-frontend.min.css
24 ms
jquery.min.js
345 ms
jquery-migrate.min.js
10 ms
custom-css.js
11 ms
jquery.bind-first-0.2.3.min.js
10 ms
js.cookie-2.1.3.min.js
22 ms
public.js
23 ms
flickity.min.css
15 ms
style.min.css
26 ms
jquery-confirm.min.css
28 ms
bootstrap-select.min.css
34 ms
pix-essentials-style-2.css
29 ms
4400891.js
64 ms
rpb.js
17 ms
wrapper-link.js
15 ms
popper.min.js
16 ms
bootstrap.min.js
28 ms
bootstrap-select.min.js
32 ms
flickity.pkgd.min.js
28 ms
core.min.js
39 ms
essentials.min.js
40 ms
v2.js
75 ms
webpack-pro.runtime.min.js
38 ms
webpack.runtime.min.js
42 ms
frontend-modules.min.js
52 ms
jquery.sticky.min.js
67 ms
frontend.min.js
50 ms
waypoints.min.js
50 ms
frontend.min.js
60 ms
elements-handlers.min.js
59 ms
v84a3a4012de94ce1a686ba8c167c359c1696973893317
67 ms
gtm.js
310 ms
Docline-Logo.svg
280 ms
CV-1.svg
321 ms
RE.svg
281 ms
ESIA.svg
279 ms
GP.svg
282 ms
Asegu.svg
279 ms
Hospi.svg
285 ms
Empr.svg
283 ms
residencias.png
284 ms
Circulo@2x.png
418 ms
Circulo.svg
286 ms
arcos.svg
287 ms
Doctora-con-movil.png
293 ms
paciente.svg
288 ms
bolas.svg
294 ms
Grupo-13912.png
298 ms
Check.svg
296 ms
doctor@2x-2.png
296 ms
Grupo-13919.png
298 ms
Group-2308.svg
299 ms
Group-2309.svg
300 ms
Group-2310.svg
302 ms
Group-2311.svg
303 ms
Asset-2.svg
304 ms
Asset-6.svg
309 ms
Asset-7.svg
306 ms
Asset-8.svg
305 ms
Tecnologia@2x.png
631 ms
CIRCLES-1.svg
309 ms
logo-blanco.svg
311 ms
DocLine-3-2-300x257.png
420 ms
Arc.svg
247 ms
Group-2312.png
249 ms
Arc2.svg
248 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf
250 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf
249 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf
141 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf
139 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf
138 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf
139 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf
138 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf
137 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf
136 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
136 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
135 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
190 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
130 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
188 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
186 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
186 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
187 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
185 ms
pixicon.ttf
655 ms
insight.min.js
85 ms
js
57 ms
analytics.js
109 ms
stat.js
117 ms
fb.js
114 ms
4400891.js
157 ms
banner.js
132 ms
collectedforms.js
133 ms
beacon-v2.helpscout.net
120 ms
landing
82 ms
collect
37 ms
vendor.cd87fe5a.js
3 ms
main.e33f799b.js
6 ms
docline.es 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
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.
docline.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
docline.es SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docline.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Docline.es 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.
docline.es
Open Graph data is detected on the main page of Docline. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: