Tools & Wizards About Us
pongee.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

pongee.com

RFID Modules, Access Control & Electric Locks | OEM/ODM R&D Manufacturer - PONGEE

Page Load Speed

8.3 sec in total

First Response

497 ms

Resources Loaded

6.1 sec

Page Rendered

1.7 sec

pongee.com screenshot

About Website

Visit pongee.com now to see the best up-to-date PONGEE content for Vietnam and also check out these interesting facts you probably never knew about pongee.com

42+ years R&D manufacturer of premium RFID modules, access hardware & electric locks. Custom OEM/ODM solutions widely applied in Smart Buildings, Healthcare, Retail, Logistics & Automation.

Visit pongee.com

Key Findings

We analyzed Pongee.com page load time and found that the first response time was 497 ms and then it took 7.8 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

pongee.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value34.0 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value1.138

1/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

pongee.com

497 ms

www.pongee.com

99 ms

www.pongee.com

702 ms

validationEngine.jquery.css

807 ms

style.css

1184 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 75% of them (39 requests) were addressed to the original Pongee.com, 23% (12 requests) were made to Goshop.gtut.com.tw and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Pongee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 929.4 kB (18%)

Content Size

5.1 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 47.1 kB

  • Original 57.4 kB
  • After minification 56.2 kB
  • After compression 10.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 47.1 kB or 82% of the original size.

Image Optimization

-18%

Potential reduce by 832.1 kB

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

JavaScript Optimization

-14%

Potential reduce by 36.6 kB

  • Original 270.2 kB
  • After minification 270.2 kB
  • After compression 233.6 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 36.6 kB or 14% of the original size.

CSS Optimization

-13%

Potential reduce by 13.7 kB

  • Original 103.7 kB
  • After minification 100.0 kB
  • After compression 90.1 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. Pongee.com needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 13% of the original size.

Requests Breakdown

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

Requests Now

44

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pongee.com

pongee.com

497 ms

www.pongee.com

www.pongee.com

99 ms

www.pongee.com

www.pongee.com

702 ms

validationEngine.jquery.css

validationEngine.jquery.css

807 ms

style.css

style.css

1184 ms

style_custom.css

style_custom.css

1006 ms

socicon-style.css

socicon-style.css

802 ms

gdpr.js

gdpr.js

811 ms

gdpr.init.js

gdpr.init.js

806 ms

js

js

75 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

983 ms

jquery.validationEngine-en-US.js

jquery.validationEngine-en-US.js

812 ms

jquery.validationEngine.min.js

jquery.validationEngine.min.js

1534 ms

socialMedia.js

socialMedia.js

994 ms

globaldefault.js

globaldefault.js

1535 ms

plugins.js

plugins.js

1382 ms

default.js

default.js

1385 ms

active.js

active.js

831 ms

logo.png

logo.png

743 ms

menu-deco-left.png

menu-deco-left.png

150 ms

menu-deco-right.png

menu-deco-right.png

137 ms

sec-menu-deco-1.png

sec-menu-deco-1.png

743 ms

sec-menu-deco-2.png

sec-menu-deco-2.png

151 ms

menu-deco-drop-top.png

menu-deco-drop-top.png

151 ms

menu-deco-drop-bottom.png

menu-deco-drop-bottom.png

150 ms

en-US.svg

en-US.svg

713 ms

zh-TW.svg

zh-TW.svg

885 ms

h4-deco-wifi.png

h4-deco-wifi.png

150 ms

h4-deco-sq.png

h4-deco-sq.png

877 ms

Case-Studies-bg.png

Case-Studies-bg.png

237 ms

dots-bg.png

dots-bg.png

257 ms

footer-pic.png

footer-pic.png

268 ms

Oxanium-VariableFont_wght.ttf

Oxanium-VariableFont_wght.ttf

1239 ms

fa-solid-900.woff

fa-solid-900.woff

1854 ms

fa-regular-400.woff

fa-regular-400.woff

1524 ms

Socicon.ttf

Socicon.ttf

1886 ms

Material-Design-Iconic-Font.woff

Material-Design-Iconic-Font.woff

1300 ms

Guard-Patrol-Tour-Terminal-PPT-350NM0-E3.jpg

Guard-Patrol-Tour-Terminal-PPT-350NM0-E3.jpg

547 ms

banner-1E.jpg

banner-1E.jpg

608 ms

BANNNER-PP-22E.jpg

BANNNER-PP-22E.jpg

646 ms

BANNER-PP-810E2.jpg

BANNER-PP-810E2.jpg

683 ms

Banner-lg-6750V1.jpg

Banner-lg-6750V1.jpg

710 ms

Banner-lg-edited-2.jpg

Banner-lg-edited-2.jpg

746 ms

Banner-lg-edited-10.jpg

Banner-lg-edited-10.jpg

776 ms

Banner-lg-310V-3.jpg

Banner-lg-310V-3.jpg

810 ms

Banner-lg-IR3.jpg

Banner-lg-IR3.jpg

832 ms

banner-M3controller-E1.jpg

banner-M3controller-E1.jpg

875 ms

Banner-lg-PC30-2.jpg

Banner-lg-PC30-2.jpg

948 ms

about-pic-edited-1.png

about-pic-edited-1.png

970 ms

tarteaucitron.css

tarteaucitron.css

744 ms

tarteaucitron.en.js

tarteaucitron.en.js

737 ms

tarteaucitron.services.js

tarteaucitron.services.js

743 ms

Accessibility Review

pongee.com accessibility score

70

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-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

SEO Factors

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

pongee.com

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