Tools & Wizards About Us
docline.es screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

docline.es

Docline - La Plataforma de Telemedicina más completa del mercado

Page Load Speed

3.4 sec in total

First Response

117 ms

Resources Loaded

2.4 sec

Page Rendered

903 ms

docline.es screenshot

About Website

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.es

Key Findings

We analyzed Docline.es page load time and found that the first response time was 117 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

docline.es performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.537

14/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

www.docline.com

117 ms

www.docline.com

491 ms

gtm.js

74 ms

uc.js

56 ms

style.min.css

378 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Docline.es, 18% (18 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (987 ms) relates to the external source Docline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 432.6 kB (37%)

Content Size

1.2 MB

After Optimization

749.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Docline.es main page is 1.2 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. 70% of websites need less resources to load. HTML takes 369.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 317.7 kB

  • Original 369.8 kB
  • After minification 369.5 kB
  • After compression 52.1 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 317.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 329.6 kB
  • After minification 329.6 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. Docline images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 55.5 kB

  • Original 315.1 kB
  • After minification 315.1 kB
  • After compression 259.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 55.5 kB or 18% of the original size.

CSS Optimization

-35%

Potential reduce by 59.4 kB

  • Original 168.0 kB
  • After minification 139.8 kB
  • After compression 108.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 59.4 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (55%)

Requests Now

80

After Optimization

36

  • Images
  • JavaScript
  • CSS

The browser has sent 80 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 32 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.docline.com

www.docline.com

117 ms

www.docline.com

www.docline.com

491 ms

gtm.js

gtm.js

74 ms

uc.js

uc.js

56 ms

style.min.css

style.min.css

378 ms

styles.css

styles.css

286 ms

common.css

common.css

292 ms

bootstrap.min.css

bootstrap.min.css

427 ms

custom-frontend.min.css

custom-frontend.min.css

369 ms

custom-pro-frontend.min.css

custom-pro-frontend.min.css

184 ms

css

css

48 ms

jquery.min.js

jquery.min.js

299 ms

jquery-migrate.min.js

jquery-migrate.min.js

384 ms

custom-css.js

custom-css.js

383 ms

flickity.min.css

flickity.min.css

305 ms

style.min.css

style.min.css

452 ms

jquery-confirm.min.css

jquery-confirm.min.css

454 ms

bootstrap-select.min.css

bootstrap-select.min.css

453 ms

css

css

22 ms

css

css

25 ms

pix-essentials-style-2.css

pix-essentials-style-2.css

666 ms

4400891.js

4400891.js

87 ms

index.js

index.js

454 ms

index.js

index.js

455 ms

rpb.js

rpb.js

624 ms

wrapper-link.js

wrapper-link.js

623 ms

popper.min.js

popper.min.js

665 ms

bootstrap.min.js

bootstrap.min.js

718 ms

bootstrap-select.min.js

bootstrap-select.min.js

808 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

823 ms

core.min.js

core.min.js

820 ms

essentials.min.js

essentials.min.js

825 ms

v2.js

v2.js

51 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

821 ms

webpack.runtime.min.js

webpack.runtime.min.js

820 ms

frontend-modules.min.js

frontend-modules.min.js

823 ms

jquery.sticky.min.js

jquery.sticky.min.js

984 ms

frontend.min.js

frontend.min.js

984 ms

waypoints.min.js

waypoints.min.js

985 ms

frontend.min.js

frontend.min.js

984 ms

elements-handlers.min.js

elements-handlers.min.js

987 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

55 ms

Docline-Logo.svg

Docline-Logo.svg

624 ms

CV-1.svg

CV-1.svg

625 ms

RE.svg

RE.svg

627 ms

GP.svg

GP.svg

625 ms

Group-2310.svg

Group-2310.svg

627 ms

Asegu.svg

Asegu.svg

629 ms

Hospi.svg

Hospi.svg

631 ms

Empr.svg

Empr.svg

673 ms

residencias.png

residencias.png

757 ms

Circulo@2x.png

Circulo@2x.png

757 ms

Circulo.svg

Circulo.svg

758 ms

arcos.svg

arcos.svg

759 ms

Doctora-con-movil.png

Doctora-con-movil.png

798 ms

paciente.svg

paciente.svg

752 ms

bolas.svg

bolas.svg

694 ms

Grupo-13912.png

Grupo-13912.png

766 ms

Check.svg

Check.svg

710 ms

doctor@2x-2.png

doctor@2x-2.png

714 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf

352 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf

357 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf

358 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf

355 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeAZ9hjQ.ttf

356 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf

355 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf

353 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYAZ9hjQ.ttf

358 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYAZ9hjQ.ttf

360 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

358 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

358 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

360 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

360 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

360 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

361 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

360 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

362 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

361 ms

Grupo-13919.png

Grupo-13919.png

789 ms

Group-2308.svg

Group-2308.svg

637 ms

Group-2309.svg

Group-2309.svg

646 ms

pixicon.ttf

pixicon.ttf

778 ms

Group-2311.svg

Group-2311.svg

574 ms

Asset-2.svg

Asset-2.svg

503 ms

Asset-6.svg

Asset-6.svg

528 ms

Asset-7.svg

Asset-7.svg

546 ms

Asset-8.svg

Asset-8.svg

542 ms

Tecnologia@2x.png

Tecnologia@2x.png

659 ms

CIRCLES-1.svg

CIRCLES-1.svg

578 ms

logo-blanco.svg

logo-blanco.svg

606 ms

DocLine-3-2-300x257.png

DocLine-3-2-300x257.png

590 ms

Arc.svg

Arc.svg

498 ms

Group-2312.png

Group-2312.png

530 ms

Arc2.svg

Arc2.svg

544 ms

insight.min.js

insight.min.js

67 ms

banner.js

banner.js

174 ms

4400891.js

4400891.js

157 ms

fb.js

fb.js

39 ms

collectedforms.js

collectedforms.js

144 ms

insight_tag_errors.gif

insight_tag_errors.gif

78 ms

beacon-v2.helpscout.net

beacon-v2.helpscout.net

19 ms

Accessibility Review

docline.es accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

docline.es best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

docline.es SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    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.

Social Sharing Optimization

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: