Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

jpnn.com

Berita Terbaru Terkini dan Terpopuler Hari Ini - JPNN.com

Page Load Speed

10.8 sec in total

First Response

1.7 sec

Resources Loaded

8.4 sec

Page Rendered

751 ms

jpnn.com screenshot

About Website

Click here to check amazing JPNN content for Indonesia. Otherwise, check out these important facts you probably never knew about jpnn.com

JPNN.com : Berita terbaru hari ini Indonesia, menyajikan kabar berita terupdate dan terpopuler seputar berita politik, ekonomi, kriminal, travel, olahraga...

Visit jpnn.com

Key Findings

We analyzed Jpnn.com page load time and found that the first response time was 1.7 sec and then it took 9.1 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

jpnn.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value2,120 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

jpnn.com

1695 ms

jawapos3.css

613 ms

2_main_style.css

918 ms

ramadhan_style.css

625 ms

platform.js

150 ms

Our browser made a total of 288 requests to load all elements on the main page. We found that 8% of them (23 requests) were addressed to the original Jpnn.com, 26% (75 requests) were made to Assets2.jpnn.com and 7% (19 requests) were made to Bh.contextweb.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Assets2.jpnn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 995.1 kB (35%)

Content Size

2.8 MB

After Optimization

1.8 MB

In fact, the total size of Jpnn.com main page is 2.8 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. 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. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 108.6 kB

  • Original 133.4 kB
  • After minification 112.3 kB
  • After compression 24.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. This page needs HTML code to be minified as it can gain 21.1 kB, which is 16% 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 108.6 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 131.7 kB

  • Original 1.6 MB
  • After minification 1.4 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. JPNN images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 580.5 kB

  • Original 903.0 kB
  • After minification 853.5 kB
  • After compression 322.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 580.5 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 174.2 kB

  • Original 209.3 kB
  • After minification 156.8 kB
  • After compression 35.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. Jpnn.com needs all CSS files to be minified and compressed as it can save up to 174.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 144 (53%)

Requests Now

271

After Optimization

127

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

Accessibility Review

jpnn.com accessibility score

89

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.

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.

Best Practices

jpnn.com 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

jpnn.com SEO score

99

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jpnn.com 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 Jpnn.com 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 JPNN. 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: