Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

extragr.am

HonestDocs: Info Kesehatan, Tanya Dokter, Pengiriman Obat | HonestDocs

Page Load Speed

7.7 sec in total

First Response

535 ms

Resources Loaded

2.7 sec

Page Rendered

4.5 sec

extragr.am screenshot

About Website

Welcome to extragr.am homepage info - get ready to check Extragr best content for Indonesia right away, or after learning these important things about extragr.am

Dapatkan informasi kesehatan terlengkap, fitur tanya jawab dokter, hingga booking rumah sakit online di HonestDocs. Klik di sini untuk memulai!

Visit extragr.am

Key Findings

We analyzed Extragr.am page load time and found that the first response time was 535 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

extragr.am performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value1,860 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

extragr.am

535 ms

www.honestdocs.id

610 ms

application_id-601c13662f3dcaf057a71e6efe5a69e11507d9f1583d343e0161a4f3b372e7ae.css

395 ms

copypastesubscribeformlogic.js

149 ms

application-af3b52121cdb98e6e9381af644a6e6e111b482bdea6cc3be4f207a867e560b98.js

1094 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Extragr.am, 51% (20 requests) were made to Honestdocs.id and 44% (17 requests) were made to Static.honestdocs.id. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.honestdocs.id.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.9 kB (11%)

Content Size

793.7 kB

After Optimization

709.8 kB

In fact, the total size of Extragr.am main page is 793.7 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. 70% of websites need less resources to load. Javascripts take 375.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 83.9 kB

  • Original 100.3 kB
  • After minification 100.0 kB
  • After compression 16.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 83.9 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 15 B

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

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 375.3 kB
  • After minification 375.3 kB
  • After compression 375.3 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 0 B

  • Original 133.1 kB
  • After minification 133.1 kB
  • After compression 133.1 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. Extragr.am has all CSS files already compressed.

Requests Breakdown

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

Requests Now

20

After Optimization

14

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

Accessibility Review

extragr.am accessibility score

55

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

[id] attributes on active, focusable elements are not unique

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

extragr.am best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

extragr.am SEO score

88

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ID

  • Language Claimed

    ID

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Extragr.am can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it matches the claimed language. Our system also found out that Extragr.am 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 data is detected on the main page of Extragr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: