Tools & Wizards About Us
staging.hamrodoctor.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

staging.hamrodoctor.com

First Online Healthcare Service Provider from Nepal

Page Load Speed

7.6 sec in total

First Response

1.1 sec

Resources Loaded

5.8 sec

Page Rendered

693 ms

staging.hamrodoctor.com screenshot

About Website

Click here to check amazing Staging Hamrodoctor content for Nepal. Otherwise, check out these important facts you probably never knew about staging.hamrodoctor.com

Hamro doctor is the first Online Healthcare Service Provider from Nepal where patients can consult certified medical personnel and get additional health related services along with other information r...

Visit staging.hamrodoctor.com

Key Findings

We analyzed Staging.hamrodoctor.com page load time and found that the first response time was 1.1 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

staging.hamrodoctor.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.137

80/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

staging.hamrodoctor.com

1058 ms

css2

120 ms

remixicon.css

120 ms

intlTelInput.min.css

141 ms

select2.min.css

127 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 43% of them (41 requests) were addressed to the original Staging.hamrodoctor.com, 14% (13 requests) were made to Embed.tawk.to and 10% (10 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Staging.hamrodoctor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 248.4 kB (20%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Staging.hamrodoctor.com main page is 1.3 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. Images take 790.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 43.9 kB

  • Original 53.0 kB
  • After minification 36.1 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 16.9 kB, which is 32% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.9 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 58.2 kB

  • Original 790.5 kB
  • After minification 732.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. Staging Hamrodoctor images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 145.6 kB

  • Original 406.4 kB
  • After minification 406.4 kB
  • After compression 260.9 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 145.6 kB or 36% of the original size.

CSS Optimization

-8%

Potential reduce by 797 B

  • Original 9.5 kB
  • After minification 9.5 kB
  • After compression 8.7 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. Staging.hamrodoctor.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

88

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

staging.hamrodoctor.com

staging.hamrodoctor.com

1058 ms

css2

css2

120 ms

remixicon.css

remixicon.css

120 ms

intlTelInput.min.css

intlTelInput.min.css

141 ms

select2.min.css

select2.min.css

127 ms

jquery-ui.min.css

jquery-ui.min.css

137 ms

owl.carousel.min.css

owl.carousel.min.css

135 ms

jquery-ui.css

jquery-ui.css

128 ms

toastr.css

toastr.css

137 ms

sweetalert2.min.css

sweetalert2.min.css

143 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

152 ms

style.css

style.css

969 ms

custom.css

custom.css

732 ms

adsbygoogle.js

adsbygoogle.js

224 ms

email-decode.min.js

email-decode.min.js

121 ms

popper.min.js

popper.min.js

121 ms

bootstrap.min.js

bootstrap.min.js

146 ms

jquery-ui.min.js

jquery-ui.min.js

145 ms

intlTelInput.js

intlTelInput.js

172 ms

select2.min.js

select2.min.js

135 ms

owl.carousel.min.js

owl.carousel.min.js

169 ms

toastr.min.js

toastr.min.js

171 ms

sweetalert2.min.js

sweetalert2.min.js

244 ms

sweetalert2@10

sweetalert2@10

120 ms

style.js

style.js

760 ms

slick.min.js

slick.min.js

745 ms

slick.css

slick.css

723 ms

firebase-app.js

firebase-app.js

144 ms

firebase-messaging.js

firebase-messaging.js

164 ms

autocomplete.js

autocomplete.js

161 ms

js

js

169 ms

sharethis.js

sharethis.js

162 ms

font-awesome.css

font-awesome.css

30 ms

gtm.js

gtm.js

83 ms

main_logo.png

main_logo.png

654 ms

Slider%20Final.png

Slider%20Final.png

685 ms

main-s2.svg

main-s2.svg

663 ms

main-s3.svg

main-s3.svg

31 ms

main-s4.svg

main-s4.svg

634 ms

main-s.svg

main-s.svg

28 ms

image.php

image.php

955 ms

image.php

image.php

32 ms

image.php

image.php

33 ms

image.php

image.php

71 ms

red.png

red.png

71 ms

gray.png

gray.png

73 ms

green.png

green.png

73 ms

blue.png

blue.png

74 ms

mockup.png

mockup.png

112 ms

apple.png

apple.png

113 ms

play.png

play.png

114 ms

footer-banner.png

footer-banner.png

114 ms

footerlogo.png

footerlogo.png

114 ms

pay_esewa.png

pay_esewa.png

741 ms

pay_khalti.png

pay_khalti.png

1343 ms

pay_ime.png

pay_ime.png

1607 ms

pay_fone.png

pay_fone.png

1604 ms

pay_ebanking.png

pay_ebanking.png

1603 ms

verified_visa.png

verified_visa.png

2631 ms

facebook-f.png

facebook-f.png

2623 ms

twitter.png

twitter.png

1347 ms

instagram.png

instagram.png

1356 ms

youtube.png

youtube.png

1363 ms

logo.png

logo.png

1371 ms

vayodha_logo_86x37.png

vayodha_logo_86x37.png

1607 ms

blue%20cross.png

blue%20cross.png

2764 ms

bb-logo_86x50.png

bb-logo_86x50.png

2532 ms

norvic.jpg

norvic.jpg

2933 ms

starLogo-1-111x69.png

starLogo-1-111x69.png

2613 ms

hams_hospital_86x37.png

hams_hospital_86x37.png

2448 ms

font

font

82 ms

Metropolis-Medium.ttf

Metropolis-Medium.ttf

3242 ms

remixicon.woff

remixicon.woff

79 ms

Metropolis-Bold.ttf

Metropolis-Bold.ttf

2511 ms

analytics.js

analytics.js

113 ms

fbevents.js

fbevents.js

112 ms

Metropolis-SemiBold.ttf

Metropolis-SemiBold.ttf

3094 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

68 ms

Metropolis-Light.ttf

Metropolis-Light.ttf

3115 ms

default

default

227 ms

js

js

82 ms

collect

collect

83 ms

collect

collect

28 ms

js

js

52 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

193 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

187 ms

twk-event-polyfill.js

twk-event-polyfill.js

76 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

198 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

220 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

219 ms

twk-main.js

twk-main.js

125 ms

twk-vendor.js

twk-vendor.js

262 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

399 ms

twk-chunk-common.js

twk-chunk-common.js

388 ms

twk-runtime.js

twk-runtime.js

245 ms

twk-app.js

twk-app.js

273 ms

Accessibility Review

staging.hamrodoctor.com accessibility score

70

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

<frame> or <iframe> elements do not have a title

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

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

staging.hamrodoctor.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

staging.hamrodoctor.com SEO score

85

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Staging.hamrodoctor.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Staging.hamrodoctor.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

staging.hamrodoctor.com

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