Tools & Wizards About Us
journal.bappenas.go.id screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

journal.bappenas.go.id

Jurnal Perencanaan Pembangunan: The Indonesian Journal of Development Planning

Page Load Speed

7.7 sec in total

First Response

532 ms

Resources Loaded

6 sec

Page Rendered

1.2 sec

journal.bappenas.go.id screenshot

About Website

Visit journal.bappenas.go.id now to see the best up-to-date Journal Bappenas content for Indonesia and also check out these interesting facts you probably never knew about journal.bappenas.go.id

Jurnal Perencanaan Pembangunan, The Indonesian Journal of Development Planning, Bappenas, Jurnal Bappenas, Bappenas Journal, JPP Bappenas, Perencanaan Pembangunan

Visit journal.bappenas.go.id

Key Findings

We analyzed Journal.bappenas.go.id page load time and found that the first response time was 532 ms and then it took 7.2 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

journal.bappenas.go.id performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value1,410 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.28

43/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

journal.bappenas.go.id

532 ms

jpp

636 ms

css

760 ms

css

777 ms

fontawesome.css

1040 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 65% of them (32 requests) were addressed to the original Journal.bappenas.go.id, 12% (6 requests) were made to Youtube.com and 4% (2 requests) were made to S01.flagcounter.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Journal.bappenas.go.id.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (36%)

Content Size

4.7 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Journal.bappenas.go.id main page is 4.7 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 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.5 kB

  • Original 29.0 kB
  • After minification 26.1 kB
  • After compression 6.4 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 22.5 kB or 78% of the original size.

Image Optimization

-27%

Potential reduce by 986.2 kB

  • Original 3.6 MB
  • After minification 2.7 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. Obviously, Journal Bappenas needs image optimization as it can save up to 986.2 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 322.9 kB

  • Original 613.3 kB
  • After minification 606.8 kB
  • After compression 290.4 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 322.9 kB or 53% of the original size.

CSS Optimization

-84%

Potential reduce by 359.8 kB

  • Original 427.3 kB
  • After minification 420.1 kB
  • After compression 67.5 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. Journal.bappenas.go.id needs all CSS files to be minified and compressed as it can save up to 359.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (34%)

Requests Now

44

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

journal.bappenas.go.id

journal.bappenas.go.id

532 ms

jpp

jpp

636 ms

css

css

760 ms

css

css

777 ms

fontawesome.css

fontawesome.css

1040 ms

orcidProfile.css

orcidProfile.css

781 ms

pageHeaderLogoImage_en_US.png

pageHeaderLogoImage_en_US.png

1542 ms

cover_issue_23_en_US.jpg

cover_issue_23_en_US.jpg

2493 ms

469 ms

QQPupbBi34Q

QQPupbBi34Q

119 ms

101 ms

jquery.min.js

jquery.min.js

1258 ms

jquery-ui.min.js

jquery-ui.min.js

2258 ms

popper.js

popper.js

1571 ms

util.js

util.js

1296 ms

dropdown.js

dropdown.js

1532 ms

main.js

main.js

1553 ms

make_submission5.jpg

make_submission5.jpg

1805 ms

Kementerian%20PPN%20Bappenas%20Square%20EN.png

Kementerian%20PPN%20Bappenas%20Square%20EN.png

2537 ms

logo_pppi.jpg

logo_pppi.jpg

2568 ms

bwplogo.png

bwplogo.png

3636 ms

download1.png

download1.png

2076 ms

sinta_logo.png

sinta_logo.png

2336 ms

67063-analytics-search-google-business-marketing-free-download-png-hq.png

67063-analytics-search-google-business-marketing-free-download-png-hq.png

2516 ms

garuda11.png

garuda11.png

2595 ms

neliti-blue.png

neliti-blue.png

2777 ms

pkp_index_logo.png

pkp_index_logo.png

2785 ms

lipi-website_ratio-16x9.jpg

lipi-website_ratio-16x9.jpg

2801 ms

400dpiLogo.png

400dpiLogo.png

2834 ms

onesearch2.jpg

onesearch2.jpg

2855 ms

ici2.png

ici2.png

3063 ms

logo_wcmasthead_en.png

logo_wcmasthead_en.png

3040 ms

Sertificate.png

Sertificate.png

3324 ms

ojs_brand.png

ojs_brand.png

3103 ms

462 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

36 ms

base.js

base.js

72 ms

ad_status.js

ad_status.js

153 ms

fAKQRIhHJzkWPBJbxdRG8sE_4N5ZCu5h9VOYIQm4PUM.js

fAKQRIhHJzkWPBJbxdRG8sE_4N5ZCu5h9VOYIQm4PUM.js

119 ms

embed.js

embed.js

22 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

49 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

55 ms

id

id

24 ms

Create

Create

121 ms

GenerateIT

GenerateIT

15 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2121 ms

js

js

43 ms

log_event

log_event

15 ms

Accessibility Review

journal.bappenas.go.id accessibility score

89

Accessibility Issues

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

journal.bappenas.go.id 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

High

Page has valid source maps

SEO Factors

journal.bappenas.go.id SEO score

84

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

journal.bappenas.go.id

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