Tools & Wizards About Us
heritage89.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

heritage89.com

Heritage Blasting Ozone Generators, Bath Refinishing, Permanent Non-Stain Materials (DIY) Malaysia - Exclusive Heritage (M) Sdn Bhd

Page Load Speed

9 sec in total

First Response

1 sec

Resources Loaded

7.8 sec

Page Rendered

183 ms

heritage89.com screenshot

About Website

Welcome to heritage89.com homepage info - get ready to check Heritage 89 best content right away, or after learning these important things about heritage89.com

was incorporated on October 1989. Our company is located in Seri Kembangan, Selangor, Malaysia. We provide “Bathtub Refinishing” formulation with quality, customization and avoiding shortcuts. We are ...

Visit heritage89.com

Key Findings

We analyzed Heritage89.com page load time and found that the first response time was 1 sec and then it took 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

heritage89.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.588

11/100

15%

TTI (Time to Interactive)

Value8.3 s

39/100

10%

Network Requests Diagram

heritage89.com

1042 ms

www.heritage89.com

1751 ms

font-awesome.css

79 ms

style.css

893 ms

general_v1.css

1120 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Heritage89.com, 66% (54 requests) were made to Cdn1.npcdn.net and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Cdn1.npcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.7 kB (6%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heritage89.com main page is 1.5 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 42.8 kB

  • Original 56.7 kB
  • After minification 55.8 kB
  • After compression 13.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 42.8 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 33.2 kB

  • Original 1.1 MB
  • After minification 1.1 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. Heritage 89 images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 12.9 kB

  • Original 277.9 kB
  • After minification 277.9 kB
  • After compression 265.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

-10%

Potential reduce by 6.7 kB

  • Original 67.5 kB
  • After minification 67.5 kB
  • After compression 60.8 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. Heritage89.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

66

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

heritage89.com

heritage89.com

1042 ms

www.heritage89.com

www.heritage89.com

1751 ms

font-awesome.css

font-awesome.css

79 ms

style.css

style.css

893 ms

general_v1.css

general_v1.css

1120 ms

color_style.css

color_style.css

944 ms

gumby.css

gumby.css

99 ms

sweetalert2.min.css

sweetalert2.min.css

141 ms

style.css

style.css

917 ms

banner.css

banner.css

860 ms

jquery.min.js

jquery.min.js

41 ms

jquery-migrate-3.0.0.min.js

jquery-migrate-3.0.0.min.js

31 ms

jquery-ui.css

jquery-ui.css

44 ms

jquery-ui.theme.min.css

jquery-ui.theme.min.css

154 ms

jquery.fancybox.js

jquery.fancybox.js

181 ms

jquery.fancybox.css

jquery.fancybox.css

204 ms

slick.css

slick.css

219 ms

slick-theme.css

slick-theme.css

234 ms

slick.min.js

slick.min.js

248 ms

jquery.qrcode-0.12.0.min.js

jquery.qrcode-0.12.0.min.js

266 ms

validate.min.js

validate.min.js

281 ms

janimate.js

janimate.js

298 ms

janimate.css

janimate.css

315 ms

owl.carousel.min.css

owl.carousel.min.css

332 ms

owl.theme.newpages.css

owl.theme.newpages.css

345 ms

owl.carousel.js

owl.carousel.js

364 ms

jquery.colourbrightness.min.js

jquery.colourbrightness.min.js

377 ms

animate.css

animate.css

396 ms

sweetalert2.min.js

sweetalert2.min.js

414 ms

fb-livechat-box.css

fb-livechat-box.css

1510 ms

page.js

page.js

50 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

427 ms

default.css

default.css

445 ms

nivo-slider.css

nivo-slider.css

492 ms

jquery-ui.min.js

jquery-ui.min.js

43 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

507 ms

jquery.dotdotdot.min.js

jquery.dotdotdot.min.js

524 ms

css

css

30 ms

css

css

25 ms

fb-livechat-box.css

fb-livechat-box.css

45 ms

bg.jpg

bg.jpg

1347 ms

1552633316banner1.jpg

1552633316banner1.jpg

1910 ms

1552633330banner2.jpg

1552633330banner2.jpg

1569 ms

1552633342banner3.jpg

1552633342banner3.jpg

1657 ms

141957738243bcfd46a7c17f6cc19ec1047c068048.jpg

141957738243bcfd46a7c17f6cc19ec1047c068048.jpg

1054 ms

content.jpg

content.jpg

1386 ms

fbevents.js

fbevents.js

104 ms

sm.25.html

sm.25.html

52 ms

eso.m4v434v2.js

eso.m4v434v2.js

63 ms

xfbml.customerchat.js

xfbml.customerchat.js

100 ms

menu_bg.png

menu_bg.png

1856 ms

loading.gif

loading.gif

1348 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

121 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

126 ms

1419577031content_bg.jpg

1419577031content_bg.jpg

2114 ms

default

default

173 ms

footerbg.jpg

footerbg.jpg

2684 ms

success_icon.png

success_icon.png

1543 ms

timeline.php

timeline.php

521 ms

icomoon.ttf

icomoon.ttf

1541 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2331 ms

np_add_cart.php

np_add_cart.php

835 ms

bullets.png

bullets.png

1570 ms

subscribe_newsletter.php

subscribe_newsletter.php

736 ms

style.css

style.css

1117 ms

general_v1.css

general_v1.css

1130 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

1141 ms

jquery.fancybox.js

jquery.fancybox.js

1156 ms

jquery.fancybox.css

jquery.fancybox.css

1168 ms

jquery.jscroll.min.js

jquery.jscroll.min.js

1183 ms

newsletter.css

newsletter.css

1703 ms

css

css

17 ms

css

css

26 ms

header487934.jpg

header487934.jpg

745 ms

1355912843exclusive.jpg

1355912843exclusive.jpg

110 ms

159367897396007472a38a86874654f0aaa1bcaf47.jpg

159367897396007472a38a86874654f0aaa1bcaf47.jpg

1274 ms

1592906475a146bfd175051416b7b3cd66f3d7d36d.jpg

1592906475a146bfd175051416b7b3cd66f3d7d36d.jpg

1534 ms

175051583484615.jpg

175051583484615.jpg

1667 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

4 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

9 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

6 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

5 ms

Accessibility Review

heritage89.com accessibility score

42

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

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

heritage89.com best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

heritage89.com SEO score

82

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

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

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heritage89.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 Heritage89.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

heritage89.com

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