Tools & Wizards About Us
docplanner.es screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

docplanner.es

Doctoralia - Encuentra especialista - Pide cita médica

Page Load Speed

1.5 sec in total

First Response

241 ms

Resources Loaded

998 ms

Page Rendered

286 ms

docplanner.es screenshot

About Website

Click here to check amazing Docplanner content for Spain. Otherwise, check out these important facts you probably never knew about docplanner.es

¡Encuentra un especialista médico en tu ciudad! Consulta opiniones de pacientes, pregunta a los expertos en salud y reserva ahora cita por Internet.

Visit docplanner.es

Key Findings

We analyzed Docplanner.es page load time and found that the first response time was 241 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

docplanner.es performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value5,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

docplanner.es

241 ms

docplanner.es

410 ms

www.doctoralia.es

33 ms

j.php

84 ms

OtAutoBlock.js

91 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original Docplanner.es, 63% (10 requests) were made to Platform.docplanner.com and 13% (2 requests) were made to Cookie-cdn.cookiepro.com. The less responsive or slowest element that took the longest time to load (410 ms) belongs to the original domain Docplanner.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.6 kB (28%)

Content Size

510.1 kB

After Optimization

369.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Docplanner.es main page is 510.1 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. 30% of websites need less resources to load. Javascripts take 254.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 140.5 kB

  • Original 174.8 kB
  • After minification 161.2 kB
  • After compression 34.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 140.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-0%

Potential reduce by 116 B

  • Original 254.1 kB
  • After minification 254.1 kB
  • After compression 254.0 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.

CSS Optimization

-0%

Potential reduce by 28 B

  • Original 40.9 kB
  • After minification 40.9 kB
  • After compression 40.9 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. Docplanner.es has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (50%)

Requests Now

12

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docplanner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

docplanner.es

docplanner.es

241 ms

docplanner.es

docplanner.es

410 ms

www.doctoralia.es

www.doctoralia.es

33 ms

j.php

j.php

84 ms

OtAutoBlock.js

OtAutoBlock.js

91 ms

otSDKStub.js

otSDKStub.js

114 ms

jade-dpuikitv3-b7dfdf16.css

jade-dpuikitv3-b7dfdf16.css

75 ms

jade-homepage-ab74ba95.css

jade-homepage-ab74ba95.css

78 ms

goro-homepage-a85e0776.js

goro-homepage-a85e0776.js

76 ms

jade-polyfills-29c9a05c.js

jade-polyfills-29c9a05c.js

77 ms

runtime-b5ada1ef.js

runtime-b5ada1ef.js

77 ms

jade-app-388b1351.js

jade-app-388b1351.js

79 ms

homepage-all.svg

homepage-all.svg

148 ms

homepage-bg-online-consultation.jpg

homepage-bg-online-consultation.jpg

99 ms

doctor-default-80-80.png

doctor-default-80-80.png

98 ms

homepage-pro-banner@2x.webp

homepage-pro-banner@2x.webp

98 ms

Accessibility Review

docplanner.es accessibility score

64

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

Some elements have a [tabindex] value greater than 0

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

docplanner.es SEO score

73

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

docplanner.es

Open Graph data is detected on the main page of Docplanner. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: