Tools & Wizards About Us
pgn.co.id screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

pgn.co.id

Beranda | PGN

Page Load Speed

9.3 sec in total

First Response

1.1 sec

Resources Loaded

7.7 sec

Page Rendered

535 ms

pgn.co.id screenshot

About Website

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

Website Resmi Pertamina Gas Negara

Visit pgn.co.id

Key Findings

We analyzed Pgn.co.id page load time and found that the first response time was 1.1 sec and then it took 8.3 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

pgn.co.id performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

pgn.co.id

1067 ms

pgn.co.id

1963 ms

bootstrap.min.css

1084 ms

styles.css

809 ms

jquery.1.12.4.min.js

1411 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 54% of them (36 requests) were addressed to the original Pgn.co.id, 46% (31 requests) were made to Panel.pgn.co.id. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Panel.pgn.co.id.

Page Optimization Overview & Recommendations

Page size can be reduced by 959.3 kB (13%)

Content Size

7.4 MB

After Optimization

6.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pgn.co.id main page is 7.4 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. 35% of websites need less resources to load. Images take 7.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 110.4 kB

  • Original 135.7 kB
  • After minification 104.6 kB
  • After compression 25.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 31.1 kB, which is 23% 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 110.4 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 761.1 kB

  • Original 7.1 MB
  • After minification 6.3 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, PGN needs image optimization as it can save up to 761.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-38%

Potential reduce by 51.1 kB

  • Original 135.4 kB
  • After minification 135.4 kB
  • After compression 84.3 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 51.1 kB or 38% of the original size.

CSS Optimization

-59%

Potential reduce by 36.7 kB

  • Original 62.4 kB
  • After minification 53.4 kB
  • After compression 25.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. Pgn.co.id needs all CSS files to be minified and compressed as it can save up to 36.7 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (8%)

Requests Now

59

After Optimization

54

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pgn.co.id

pgn.co.id

1067 ms

pgn.co.id

pgn.co.id

1963 ms

bootstrap.min.css

bootstrap.min.css

1084 ms

styles.css

styles.css

809 ms

jquery.1.12.4.min.js

jquery.1.12.4.min.js

1411 ms

bootstrap.min.js

bootstrap.min.js

1133 ms

home.css

home.css

1082 ms

jssor.slider.min.js

jssor.slider.min.js

816 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

279 ms

jquery.nicescroll.js

jquery.nicescroll.js

827 ms

jquery.nicescroll.plus.js

jquery.nicescroll.plus.js

559 ms

home-header.png

home-header.png

2426 ms

LogoPGNWeb170xNew01.png

LogoPGNWeb170xNew01.png

280 ms

LogoPGNNew01.png

LogoPGNNew01.png

269 ms

lang_eng.png

lang_eng.png

278 ms

lang_divider.png

lang_divider.png

279 ms

lang_idn.png

lang_idn.png

474 ms

contact-center.png

contact-center.png

475 ms

fb_logo.png

fb_logo.png

549 ms

twitter_logo.png

twitter_logo.png

556 ms

share_logo.png

share_logo.png

554 ms

wbs_icon_pgn.png

wbs_icon_pgn.png

910 ms

elhkpn.png

elhkpn.png

787 ms

insta_logo.png

insta_logo.png

745 ms

youtube_logo.png

youtube_logo.png

817 ms

tiktok_logo.png

tiktok_logo.png

833 ms

linkedin_logo.png

linkedin_logo.png

832 ms

wa_logo.png

wa_logo.png

1014 ms

button-site-map.png

button-site-map.png

1056 ms

home-header_2.png

home-header_2.png

2742 ms

home-header_3.png

home-header_3.png

2530 ms

residensial.png

residensial.png

2258 ms

bisnis.png

bisnis.png

2542 ms

transportasi.png

transportasi.png

2531 ms

slide_1_gas-app.png

slide_1_gas-app.png

2819 ms

slide_2_gas-sup.png

slide_2_gas-sup.png

2972 ms

slide_3_o-m-sol.png

slide_3_o-m-sol.png

3095 ms

slide_4_support-sis.png

slide_4_support-sis.png

3103 ms

slide_5_financial-sol.png

slide_5_financial-sol.png

3115 ms

slide_6_infra-sol.png

slide_6_infra-sol.png

3297 ms

360%20Logo.png

360%20Logo.png

3100 ms

circle_ambiance-line.png

circle_ambiance-line.png

3244 ms

circle-blue.png

circle-blue.png

3376 ms

360_text.png

360_text.png

3380 ms

72_text.png

72_text.png

3385 ms

144_text.png

144_text.png

3394 ms

216_text.png

216_text.png

3514 ms

288_text.png

288_text.png

3572 ms

image-pipa-blur.png

image-pipa-blur.png

3660 ms

tata-kelola.png

tata-kelola.png

3661 ms

keberlanjutan.png

keberlanjutan.png

3668 ms

informasi-publik.png

informasi-publik.png

3675 ms

img_video.png

img_video.png

3796 ms

ingin-berlangganan-gas.png

ingin-berlangganan-gas.png

3854 ms

pgn-mobile.jpg

pgn-mobile.jpg

3950 ms

pgn-mobile_app-store.png

pgn-mobile_app-store.png

3941 ms

pgn-mobile_google.png

pgn-mobile_google.png

3948 ms

line-header.jpg

line-header.jpg

1100 ms

helvetica-neue-lt-std-45-light.woff

helvetica-neue-lt-std-45-light.woff

1069 ms

helvetica-neue-lt-std-65-medium.woff

helvetica-neue-lt-std-65-medium.woff

1068 ms

helvetica-neue-lt-std-75-bold.woff

helvetica-neue-lt-std-75-bold.woff

1146 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1299 ms

kpgk_icon_putih.png

kpgk_icon_putih.png

1320 ms

kpgk_icon_putih2.png

kpgk_icon_putih2.png

1400 ms

kpgk_icon_putih.png

kpgk_icon_putih.png

3902 ms

kpgk_icon_putih2.png

kpgk_icon_putih2.png

4017 ms

footer.jpg

footer.jpg

1177 ms

Accessibility Review

pgn.co.id accessibility score

65

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

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

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

pgn.co.id best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pgn.co.id SEO score

75

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

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

    N/A

  • Encoding

    UTF-8

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

pgn.co.id

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