Tools & Wizards About Us
puang.com screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

puang.com

Mr. Puang | Indonesia

Page Load Speed

3.3 sec in total

First Response

177 ms

Resources Loaded

2.9 sec

Page Rendered

219 ms

puang.com screenshot

About Website

Click here to check amazing Puang content. Otherwise, check out these important facts you probably never knew about puang.com

Pribadi yang suka otak-atik seputar Informasi dan Teknologi

Visit puang.com

Key Findings

We analyzed Puang.com page load time and found that the first response time was 177 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

puang.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

26/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

puang.com

177 ms

puang.css

31 ms

getpg.js

144 ms

js.js

711 ms

jquery.bxslider.css

1721 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 52% of them (45 requests) were addressed to the original Puang.com, 9% (8 requests) were made to Apis.google.com and 8% (7 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Puang.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 588.4 kB (47%)

Content Size

1.3 MB

After Optimization

665.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 95.6 kB

  • Original 121.3 kB
  • After minification 109.0 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 95.6 kB or 79% of the original size.

Image Optimization

-10%

Potential reduce by 50.0 kB

  • Original 483.2 kB
  • After minification 433.2 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. Puang images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 427.4 kB

  • Original 629.8 kB
  • After minification 583.9 kB
  • After compression 202.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 427.4 kB or 68% of the original size.

CSS Optimization

-77%

Potential reduce by 15.4 kB

  • Original 20.0 kB
  • After minification 16.0 kB
  • After compression 4.6 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. Puang.com needs all CSS files to be minified and compressed as it can save up to 15.4 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (67%)

Requests Now

78

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

puang.com

puang.com

177 ms

puang.css

puang.css

31 ms

getpg.js

getpg.js

144 ms

js.js

js.js

711 ms

jquery.bxslider.css

jquery.bxslider.css

1721 ms

refresh.js

refresh.js

718 ms

refresh_m.js

refresh_m.js

1562 ms

jquery.bxslider.js

jquery.bxslider.js

73 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

104 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

118 ms

jquery.fancybox.js

jquery.fancybox.js

135 ms

jquery.fancybox.css

jquery.fancybox.css

149 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

155 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

163 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

167 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

176 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

181 ms

addthis_widget.js

addthis_widget.js

25 ms

platform.js

platform.js

60 ms

in.js

in.js

27 ms

9 ms

www.puang.com

www.puang.com

22 ms

171 ms

head-0614.jpg

head-0614.jpg

28 ms

twit.jpg

twit.jpg

33 ms

tw-reply.png

tw-reply.png

32 ms

tw-retweet.png

tw-retweet.png

32 ms

tw-fav.png

tw-fav.png

42 ms

edit.gif

edit.gif

45 ms

phone.png

phone.png

51 ms

location.gif

location.gif

45 ms

rss.jpg

rss.jpg

56 ms

sts_on.gif

sts_on.gif

61 ms

list-next.gif

list-next.gif

57 ms

s_lang.png

s_lang.png

63 ms

20_16x16.png

20_16x16.png

71 ms

ok.jpg

ok.jpg

83 ms

spacer.gif

spacer.gif

72 ms

sdk.js

sdk.js

306 ms

open_11.jpg

open_11.jpg

16 ms

home.php

home.php

457 ms

loading.gif

loading.gif

95 ms

secureAnonymousFramework

secureAnonymousFramework

155 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

88 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

125 ms

fastbutton

fastbutton

221 ms

widgets.js

widgets.js

82 ms

300lo.json

300lo.json

65 ms

open_13.jpg

open_13.jpg

68 ms

open_17.jpg

open_17.jpg

68 ms

open_18.jpg

open_18.jpg

68 ms

open_20.jpg

open_20.jpg

68 ms

bx_loader.gif

bx_loader.gif

68 ms

controls.png

controls.png

68 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

65 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

128 ms

postmessageRelay

postmessageRelay

146 ms

share

share

125 ms

sprite_connect_v14.png

sprite_connect_v14.png

87 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

25 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

24 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

79 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

27 ms

pixel

pixel

60 ms

pixel

pixel

58 ms

pixel

pixel

61 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

33 ms

rpc:shindig_random.js

rpc:shindig_random.js

32 ms

pixel

pixel

25 ms

pixel

pixel

26 ms

pixel

pixel

22 ms

148 ms

xd_arbiter.php

xd_arbiter.php

215 ms

xd_arbiter.php

xd_arbiter.php

438 ms

match-result

match-result

18 ms

match-result

match-result

17 ms

match-result

match-result

13 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

pixel

pixel

15 ms

jot

jot

88 ms

voip-sulbar-700-80.jpg

voip-sulbar-700-80.jpg

480 ms

49.gif

49.gif

179 ms

puang-pic.php

puang-pic.php

341 ms

news_5651fc6f6255d.twitter-count-button-gone.jpg

news_5651fc6f6255d.twitter-count-button-gone.jpg

319 ms

news_5631cf9accbdd.masker-botol-bekas.jpg

news_5631cf9accbdd.masker-botol-bekas.jpg

320 ms

tap.php

tap.php

6 ms

Accessibility Review

puang.com accessibility score

78

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

[role]s do not have all required [aria-*] attributes

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

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

Best Practices

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

puang.com SEO score

85

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

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

puang.com

Open Graph data is detected on the main page of Puang. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: