Tools & Wizards About Us
dors.app screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

dors.app

DORS - SOPS Polri

Page Load Speed

20 sec in total

First Response

520 ms

Resources Loaded

18.6 sec

Page Rendered

862 ms

dors.app screenshot

About Website

Welcome to dors.app homepage info - get ready to check DORS best content for Indonesia right away, or after learning these important things about dors.app

Daily Operational Reporting System (DORS) - SOPS Polri

Visit dors.app

Key Findings

We analyzed Dors.app page load time and found that the first response time was 520 ms and then it took 19.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.

Performance Metrics

dors.app performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

dors.app

520 ms

dors.app

4840 ms

bootstrap.min.css

2968 ms

font-awesome.min.css

3199 ms

fonts.googleapis.com.css

1251 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 83% of them (15 requests) were addressed to the original Dors.app, 11% (2 requests) were made to Fonts.gstatic.com and 6% (1 request) were made to . The less responsive or slowest element that took the longest time to load (11 sec) belongs to the original domain Dors.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 883.8 kB (68%)

Content Size

1.3 MB

After Optimization

416.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dors.app 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. 30% of websites need less resources to load. CSS take 667.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 17.0 kB

  • Original 22.8 kB
  • After minification 21.4 kB
  • After compression 5.8 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 17.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-68%

Potential reduce by 300.1 kB

  • Original 440.3 kB
  • After minification 406.7 kB
  • After compression 140.2 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 300.1 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 566.7 kB

  • Original 667.5 kB
  • After minification 667.2 kB
  • After compression 100.8 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. Dors.app needs all CSS files to be minified and compressed as it can save up to 566.7 kB or 85% of the original size.

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 DORS. 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 CSS and as a result speed up the page load time.

Network Requests Diagram

dors.app

dors.app

520 ms

dors.app

dors.app

4840 ms

bootstrap.min.css

bootstrap.min.css

2968 ms

font-awesome.min.css

font-awesome.min.css

3199 ms

fonts.googleapis.com.css

fonts.googleapis.com.css

1251 ms

ace.min.css

ace.min.css

5681 ms

ace-rtl.min.css

ace-rtl.min.css

1540 ms

login-custom.css

login-custom.css

775 ms

jquery.2.1.1.min.js

jquery.2.1.1.min.js

2723 ms

stylesheets

stylesheets

6227 ms

javascript

javascript

11043 ms

sops-fire-logo.png

sops-fire-logo.png

10974 ms

bg-1.jpg

bg-1.jpg

9914 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

7 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

7 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

237 ms

4LU3PApQABVMtB1AAA

4LU3PApQABVMtB1AAA

34 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1661 ms

Accessibility Review

dors.app accessibility score

72

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

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

dors.app 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

SEO Factors

dors.app SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    ID

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dors.app can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed English language. Our system also found out that Dors.app 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

dors.app

Open Graph description is not detected on the main page of DORS. 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: