Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

metropolitan.id

Metropolitan - News, Lifestyle, and Sport

Page Load Speed

2.7 sec in total

First Response

430 ms

Resources Loaded

1.7 sec

Page Rendered

567 ms

About Website

Welcome to metropolitan.id homepage info - get ready to check Metropolitan best content for Indonesia right away, or after learning these important things about metropolitan.id

Menyajikan berita terbaru berita hari ini, serta isu tentang Metropolitan, Jakarta, Bogor Raya, wisata kuliner, politik, olahraga, bisnis, oto tekno, hiburan

Visit metropolitan.id

Key Findings

We analyzed Metropolitan.id page load time and found that the first response time was 430 ms and then it took 2.2 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

metropolitan.id performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value4,410 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.091

92/100

15%

TTI (Time to Interactive)

Value27.4 s

0/100

10%

Network Requests Diagram

metropolitan.id

430 ms

www.metropolitan.id

38 ms

style.min.css

70 ms

style_ads.css

85 ms

all.min.css

64 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Metropolitan.id, 70% (31 requests) were made to Static.promediateknologi.id and 5% (2 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Propsid.b-cdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.6 kB (37%)

Content Size

683.1 kB

After Optimization

427.5 kB

In fact, the total size of Metropolitan.id main page is 683.1 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. 60% of websites need less resources to load. Javascripts take 457.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 150.5 kB

  • Original 168.8 kB
  • After minification 100.1 kB
  • After compression 18.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 68.7 kB, which is 41% 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 150.5 kB or 89% of the original size.

Image Optimization

-9%

Potential reduce by 2.7 kB

  • Original 31.7 kB
  • After minification 29.0 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. Metropolitan images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 77.6 kB

  • Original 457.2 kB
  • After minification 457.2 kB
  • After compression 379.6 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 77.6 kB or 17% of the original size.

CSS Optimization

-98%

Potential reduce by 24.8 kB

  • Original 25.4 kB
  • After minification 745 B
  • After compression 612 B

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. Metropolitan.id needs all CSS files to be minified and compressed as it can save up to 24.8 kB or 98% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (50%)

Requests Now

40

After Optimization

20

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

Accessibility Review

metropolitan.id accessibility score

69

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.

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

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

High

Links do not have a discernible name

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

metropolitan.id best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

metropolitan.id SEO score

83

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 Metropolitan.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 Metropolitan.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 data is detected on the main page of Metropolitan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: