Tools & Wizards About Us
puninar.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

puninar.com

Home | Puninar Logistics - Trusted Solution Partner

Page Load Speed

28.4 sec in total

First Response

479 ms

Resources Loaded

27.7 sec

Page Rendered

208 ms

puninar.com screenshot

About Website

Welcome to puninar.com homepage info - get ready to check Puninar best content for Indonesia right away, or after learning these important things about puninar.com

home,Puninar Logistics has grown and developed into foremost and experienced logistics company which leads logistics world in Indonesia with the capability and competence to provide a total logistics ...

Visit puninar.com

Key Findings

We analyzed Puninar.com page load time and found that the first response time was 479 ms and then it took 27.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

puninar.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value23.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,070 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.22

57/100

15%

TTI (Time to Interactive)

Value29.9 s

0/100

10%

Network Requests Diagram

puninar.com

479 ms

puninar.com

2057 ms

style.css

2221 ms

style.css

937 ms

slick-theme.css

724 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 48% of them (35 requests) were addressed to the original Puninar.com, 11% (8 requests) were made to Embed.tawk.to and 4% (3 requests) were made to Thrtle.com. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Puninar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (25%)

Content Size

4.4 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Puninar.com main page is 4.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. 50% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 22.1 kB

  • Original 28.2 kB
  • After minification 23.7 kB
  • After compression 6.1 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 4.5 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 22.1 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 353.3 kB

  • Original 3.2 MB
  • After minification 2.9 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, Puninar needs image optimization as it can save up to 353.3 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

-61%

Potential reduce by 628.3 kB

  • Original 1.0 MB
  • After minification 841.0 kB
  • After compression 406.1 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 628.3 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 116.0 kB

  • Original 139.6 kB
  • After minification 114.8 kB
  • After compression 23.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. Puninar.com needs all CSS files to be minified and compressed as it can save up to 116.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (62%)

Requests Now

63

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

puninar.com

puninar.com

479 ms

puninar.com

puninar.com

2057 ms

style.css

style.css

2221 ms

style.css

style.css

937 ms

slick-theme.css

slick-theme.css

724 ms

jquery-1.11.3.js

jquery-1.11.3.js

1926 ms

jquery-ui.min.js

jquery-ui.min.js

1688 ms

global.js

global.js

730 ms

jquery.fitvids.js

jquery.fitvids.js

964 ms

jquery.js

jquery.js

2259 ms

slick.js

slick.js

1403 ms

wowslider.js

wowslider.js

1683 ms

script.js

script.js

1637 ms

css

css

30 ms

opensans-regular_0-webfont.woff

opensans-regular_0-webfont.woff

1400 ms

default

default

176 ms

gtm.js

gtm.js

109 ms

logo.png

logo.png

248 ms

CC1.png

CC1.png

2405 ms

2.png

2.png

1443 ms

Warehouse_Management1.png

Warehouse_Management1.png

3343 ms

Banner_17_Agu_2021.png

Banner_17_Agu_2021.png

20214 ms

supply_chain_solutions.png

supply_chain_solutions.png

489 ms

custom_clearance2.png

custom_clearance2.png

731 ms

multimodal_transportation.png

multimodal_transportation.png

971 ms

warehouse_management.png

warehouse_management.png

1212 ms

montserrat-regular-webfont.woff

montserrat-regular-webfont.woff

1438 ms

bg-homeservice.png

bg-homeservice.png

3224 ms

bg-footer.png

bg-footer.png

2479 ms

js15_as.js

js15_as.js

94 ms

analytics.js

analytics.js

65 ms

ga.js

ga.js

92 ms

arrowright-banner.png

arrowright-banner.png

1603 ms

arrowleft-banner.png

arrowleft-banner.png

1844 ms

ajax-loader.gif

ajax-loader.gif

2085 ms

WDSy9G5kYXAAH0yK4AAAA

WDSy9G5kYXAAH0yK4AAAA

1 ms

ws-ctrl-boundary.svg

ws-ctrl-boundary.svg

2326 ms

opensans-light-webfont.woff

opensans-light-webfont.woff

2553 ms

collect

collect

33 ms

__utm.gif

__utm.gif

12 ms

4146009.php

4146009.php

83 ms

cc_430.js

cc_430.js

13 ms

220 ms

230 ms

t.dhj

t.dhj

26 ms

afwu.js

afwu.js

41 ms

427 ms

t_.htm

t_.htm

4 ms

t_.js

t_.js

3 ms

lt.min.js

lt.min.js

19 ms

empty.js

empty.js

46 ms

ProfilesEngineServlet

ProfilesEngineServlet

43 ms

1540_03681

1540_03681

58 ms

sync

sync

47 ms

IIQUniversalID-sync.js

IIQUniversalID-sync.js

24 ms

sync

sync

10 ms

cms

cms

13 ms

merge

merge

4 ms

merge

merge

4 ms

sync

sync

3 ms

52164

52164

13 ms

style768.css

style768.css

531 ms

Banner_17_Agu_2021.png

Banner_17_Agu_2021.png

1450 ms

style480.css

style480.css

468 ms

style320.css

style320.css

467 ms

twk-event-polyfill.js

twk-event-polyfill.js

93 ms

twk-main.js

twk-main.js

26 ms

twk-vendor.js

twk-vendor.js

34 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

37 ms

twk-chunk-common.js

twk-chunk-common.js

25 ms

twk-runtime.js

twk-runtime.js

22 ms

twk-app.js

twk-app.js

37 ms

optimus_rules.json

optimus_rules.json

7 ms

Accessibility Review

puninar.com accessibility score

79

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

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

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

puninar.com best practices score

50

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

High

Page has valid source maps

SEO Factors

puninar.com SEO score

98

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puninar.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Puninar.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

puninar.com

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