Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

catatan.web.id

Catatan Online Media Berita Informasi Teknologi

Page Load Speed

2.8 sec in total

First Response

372 ms

Resources Loaded

2.2 sec

Page Rendered

198 ms

catatan.web.id screenshot

About Website

Visit catatan.web.id now to see the best up-to-date Catatan content for Indonesia and also check out these interesting facts you probably never knew about catatan.web.id

Catatan Online Media Berita Informasi Teknologi dan Hiburan disertai Tips dan Trik Menarik.

Visit catatan.web.id

Key Findings

We analyzed Catatan.web.id page load time and found that the first response time was 372 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

catatan.web.id performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

26/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value4,190 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

catatan.web.id

372 ms

www.catatan.web.id

556 ms

3645911276-widget_css_bundle.css

65 ms

authorization.css

115 ms

plusone.js

101 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Catatan.web.id, 22% (27 requests) were made to Apis.google.com and 16% (20 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (832 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.0 kB (41%)

Content Size

496.4 kB

After Optimization

292.4 kB

In fact, the total size of Catatan.web.id main page is 496.4 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. 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. Javascripts take 180.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 125.7 kB

  • Original 151.5 kB
  • After minification 150.4 kB
  • After compression 25.7 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 125.7 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 3.7 kB

  • Original 113.1 kB
  • After minification 109.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. Catatan images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 38.5 kB

  • Original 180.0 kB
  • After minification 179.8 kB
  • After compression 141.5 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 38.5 kB or 21% of the original size.

CSS Optimization

-70%

Potential reduce by 36.1 kB

  • Original 51.8 kB
  • After minification 51.3 kB
  • After compression 15.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. Catatan.web.id needs all CSS files to be minified and compressed as it can save up to 36.1 kB or 70% of the original size.

Requests Breakdown

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

Requests Now

116

After Optimization

61

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

Accessibility Review

catatan.web.id accessibility score

58

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

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

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

catatan.web.id best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

catatan.web.id SEO score

77

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

Links do not have descriptive text

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ID

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Catatan.web.id can be misinterpreted by Google and other search engines. Our service has detected that 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 Catatan.web.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 Catatan. 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: