Tools & Wizards About Us
polyplassb.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

polyplassb.com

Malaysia Penang Plastic Injection Moulding, Precision / Engineering Plastic Parts, Mould and Die in Pulau Pinang, Malaysia

Page Load Speed

4.6 sec in total

First Response

700 ms

Resources Loaded

3.8 sec

Page Rendered

92 ms

polyplassb.com screenshot

About Website

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

Located in Penang Malaysia, Polyplas Sdn Bhd provides a complete range of processing techniques for the injection moulding of plastics

Visit polyplassb.com

Key Findings

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

Performance Metrics

polyplassb.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

polyplassb.com

700 ms

main.css

240 ms

navistyle.css

475 ms

nivo-slider.css

473 ms

jquery.min.js

7 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 89% of them (34 requests) were addressed to the original Polyplassb.com, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Polyplassb.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.7 kB (1%)

Content Size

1.8 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-70%

Potential reduce by 8.8 kB

  • Original 12.7 kB
  • After minification 12.0 kB
  • After compression 3.9 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 8.8 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 4.2 kB

  • Original 1.7 MB
  • After minification 1.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. Polyplassb images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 9.1 kB

  • Original 88.2 kB
  • After minification 88.2 kB
  • After compression 79.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-46%

Potential reduce by 2.5 kB

  • Original 5.5 kB
  • After minification 5.5 kB
  • After compression 2.9 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. Polyplassb.com needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (46%)

Requests Now

37

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

polyplassb.com

polyplassb.com

700 ms

main.css

main.css

240 ms

navistyle.css

navistyle.css

475 ms

nivo-slider.css

nivo-slider.css

473 ms

jquery.min.js

jquery.min.js

7 ms

navi.js

navi.js

472 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

481 ms

scrolltopcontrol.js

scrolltopcontrol.js

480 ms

WebResource.axd

WebResource.axd

483 ms

ScriptResource.axd

ScriptResource.axd

1178 ms

ScriptResource.axd

ScriptResource.axd

945 ms

element.js

element.js

47 ms

imgbkg.jpg

imgbkg.jpg

236 ms

imglogo.png

imglogo.png

472 ms

linkedin.png

linkedin.png

238 ms

img01.jpg

img01.jpg

1431 ms

img02.jpg

img02.jpg

1427 ms

img03.jpg

img03.jpg

2155 ms

img04.jpg

img04.jpg

1648 ms

img05.jpg

img05.jpg

1435 ms

img06.jpg

img06.jpg

1644 ms

img07.jpg

img07.jpg

1677 ms

imgmaindco01.jpg

imgmaindco01.jpg

1680 ms

imgcontact.jpg

imgcontact.jpg

1681 ms

imglogo2.jpg

imglogo2.jpg

1879 ms

imgnavileft.png

imgnavileft.png

1171 ms

imgnavicen.png

imgnavicen.png

1200 ms

imghover.png

imghover.png

1202 ms

imgnavidevider.png

imgnavidevider.png

1203 ms

imgnavicen2.png

imgnavicen2.png

1401 ms

imgnaviright.png

imgnaviright.png

1406 ms

imgslideshadow.jpg

imgslideshadow.jpg

1435 ms

imgloading.gif

imgloading.gif

1439 ms

ga.js

ga.js

9 ms

imgblank.png

imgblank.png

1424 ms

back-to-top.png

back-to-top.png

1622 ms

__utm.gif

__utm.gif

11 ms

imgarrows.png

imgarrows.png

237 ms

Accessibility Review

polyplassb.com accessibility score

79

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

polyplassb.com SEO score

62

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

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

polyplassb.com

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