Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    56% of websites

pajak.go.id

Direktorat Jenderal Pajak

Page Load Speed

78.6 sec in total

First Response

14.2 sec

Resources Loaded

63.8 sec

Page Rendered

646 ms

pajak.go.id screenshot

About Website

Click here to check amazing Pajak content for Indonesia. Otherwise, check out these important facts you probably never knew about pajak.go.id

Live Chat DJP

Visit pajak.go.id

Key Findings

We analyzed Pajak.go.id page load time and found that the first response time was 14.2 sec and then it took 64.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

pajak.go.id performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value25.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value71.8 s

0/100

25%

SI (Speed Index)

Value45.3 s

0/100

10%

TBT (Total Blocking Time)

Value5,050 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.482

17/100

15%

TTI (Time to Interactive)

Value134.2 s

0/100

10%

Network Requests Diagram

pajak.go.id

14186 ms

analytics.js

21 ms

css

72 ms

normalize.css

734 ms

normalize-fixes.css

743 ms

Our browser made a total of 277 requests to load all elements on the main page. We found that 79% of them (219 requests) were addressed to the original Pajak.go.id, 7% (19 requests) were made to Youtube.com and 4% (12 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Pajak.go.id.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (47%)

Content Size

5.4 MB

After Optimization

2.9 MB

In fact, the total size of Pajak.go.id main page is 5.4 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. 80% 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 141.7 kB

  • Original 169.0 kB
  • After minification 135.8 kB
  • After compression 27.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. This page needs HTML code to be minified as it can gain 33.2 kB, which is 20% 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 141.7 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 173.5 kB

  • Original 2.2 MB
  • After minification 2.0 MB

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. Pajak images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 1.3 MB

  • Original 2.0 MB
  • After minification 1.9 MB
  • After compression 674.7 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 1.3 MB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 889.7 kB

  • Original 1.1 MB
  • After minification 912.8 kB
  • After compression 188.2 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. Pajak.go.id needs all CSS files to be minified and compressed as it can save up to 889.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 154 (59%)

Requests Now

259

After Optimization

105

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

Accessibility Review

pajak.go.id accessibility score

71

Accessibility Issues

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

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.

SEO Factors

pajak.go.id 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

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 Pajak.go.id 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 Pajak.go.id 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 Pajak. 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: