Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

hotdoc.com

Find a Doctor, GP, Dentist or Healthcare Specialist near you - HotDoc

Page Load Speed

3.2 sec in total

First Response

422 ms

Resources Loaded

2.7 sec

Page Rendered

57 ms

hotdoc.com screenshot

About Website

Click here to check amazing Hot Doc content for Australia. Otherwise, check out these important facts you probably never knew about hotdoc.com

Book an online appointment with your preferred healthcare provider all over Australia. See up to date availability and book instantly.

Visit hotdoc.com

Key Findings

We analyzed Hotdoc.com page load time and found that the first response time was 422 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

hotdoc.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

hotdoc.com

422 ms

hotdoc.com

796 ms

www.hotdoc.com.au

813 ms

vendor.7e2edff659103cb7948c0045f98b9794.css

60 ms

chunk.6eb68babdd24a6f7f5fc.css

65 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 15% of them (2 requests) were addressed to the original Hotdoc.com, 77% (10 requests) were made to Cdn.hotdoc.com.au and 8% (1 request) were made to Hotdoc.com.au. The less responsive or slowest element that took the longest time to load (813 ms) relates to the external source Hotdoc.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.6 kB (40%)

Content Size

24.2 kB

After Optimization

14.6 kB

In fact, the total size of Hotdoc.com main page is 24.2 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. 25% of websites need less resources to load. HTML takes 13.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 9.5 kB

  • Original 13.9 kB
  • After minification 13.6 kB
  • After compression 4.4 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 9.5 kB or 69% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 9.8 kB
  • After minification 9.8 kB
  • After compression 9.8 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

-11%

Potential reduce by 63 B

  • Original 548 B
  • After minification 548 B
  • After compression 485 B

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. Hotdoc.com needs all CSS files to be minified and compressed as it can save up to 63 B or 11% of the original size.

Requests Breakdown

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

Requests Now

8

After Optimization

4

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

Accessibility Review

hotdoc.com accessibility score

100

Accessibility Issues

Best Practices

hotdoc.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

hotdoc.com SEO score

93

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotdoc.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 Hotdoc.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Hot Doc. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: