Tools & Wizards About Us
napure.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

napure.com

The Largest Natural Latex Bedding Manufacturer in Malaysia | Napure

Page Load Speed

11.1 sec in total

First Response

2.3 sec

Resources Loaded

8 sec

Page Rendered

668 ms

napure.com screenshot

About Website

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

Napure is a German registered brand owned by Malaysia's largest natural latex manufacturer, LSK Mattressworld Sdn. Bhd. and LSK Mattress Marketing Sdn. Bhd.

Visit napure.com

Key Findings

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

napure.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.2 s

0/100

25%

SI (Speed Index)

Value21.1 s

0/100

10%

TBT (Total Blocking Time)

Value600 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value26.8 s

0/100

10%

Network Requests Diagram

www.napure.com

2347 ms

wp-emoji-release.min.js

691 ms

style.min.css

920 ms

style.css

924 ms

jquery.selectBox.css

708 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 73% of them (74 requests) were addressed to the original Napure.com, 13% (13 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Napure.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (26%)

Content Size

6.7 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Napure.com main page is 6.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 67.3 kB

  • Original 83.7 kB
  • After minification 77.7 kB
  • After compression 16.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 67.3 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 27.5 kB

  • Original 4.2 MB
  • After minification 4.2 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. Napure images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 537.4 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 480.5 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 537.4 kB or 53% of the original size.

CSS Optimization

-86%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 184.5 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. Napure.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (70%)

Requests Now

83

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.napure.com

www.napure.com

2347 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

691 ms

style.min.css

style.min.css

920 ms

style.css

style.css

924 ms

jquery.selectBox.css

jquery.selectBox.css

708 ms

font-awesome.min.css

font-awesome.min.css

948 ms

style.css

style.css

947 ms

styles.css

styles.css

928 ms

settings.css

settings.css

1180 ms

woocommerce-layout.css

woocommerce-layout.css

1152 ms

woocommerce.css

woocommerce.css

1181 ms

quform.css

quform.css

1202 ms

colorbox.css

colorbox.css

976 ms

prettyPhoto.css

prettyPhoto.css

977 ms

font-awesome.min.css

font-awesome.min.css

1175 ms

style.css

style.css

1209 ms

owl.carousel.css

owl.carousel.css

1213 ms

owl.theme.css

owl.theme.css

1214 ms

css

css

38 ms

noo.css

noo.css

1878 ms

style.css

style.css

1410 ms

custom.css

custom.css

1440 ms

magnific-popup.css

magnific-popup.css

1445 ms

noo-megamenu.css

noo-megamenu.css

1448 ms

js_composer.min.css

js_composer.min.css

2190 ms

jquery.js

jquery.js

1877 ms

jquery-migrate.min.js

jquery-migrate.min.js

1677 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1923 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1928 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1916 ms

add-to-cart.min.js

add-to-cart.min.js

2107 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

2106 ms

modernizr-2.7.1.min.js

modernizr-2.7.1.min.js

2154 ms

js

js

47 ms

js

js

90 ms

css

css

31 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

1935 ms

jquery.yith-wcwl.js

jquery.yith-wcwl.js

2157 ms

scripts.js

scripts.js

2158 ms

api.js

api.js

31 ms

js.cookie.min.js

js.cookie.min.js

2187 ms

woocommerce.min.js

woocommerce.min.js

1945 ms

cart-fragments.min.js

cart-fragments.min.js

1929 ms

quform.js

quform.js

1754 ms

woocompare.min.js

woocompare.min.js

1858 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

1860 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

1924 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1921 ms

infinitescroll-2.0.2.min.js

infinitescroll-2.0.2.min.js

1717 ms

off-cavnas.js

off-cavnas.js

1714 ms

noo_new.js

noo_new.js

1829 ms

noo.js

noo.js

1836 ms

wp-embed.min.js

wp-embed.min.js

1721 ms

js_composer_front.min.js

js_composer_front.min.js

1719 ms

fbevents.js

fbevents.js

73 ms

cropped-logo.jpg

cropped-logo.jpg

716 ms

home-slider.jpg

home-slider.jpg

927 ms

S6uyw4BMUTPHjxAwWw.ttf

S6uyw4BMUTPHjxAwWw.ttf

90 ms

S6u9w4BMUTPHh7USSwaPHA.ttf

S6u9w4BMUTPHh7USSwaPHA.ttf

90 ms

S6u8w4BMUTPHh30AUi-v.ttf

S6u8w4BMUTPHh30AUi-v.ttf

112 ms

S6u9w4BMUTPHh6UVSwaPHA.ttf

S6u9w4BMUTPHh6UVSwaPHA.ttf

120 ms

S6u9w4BMUTPHh50XSwaPHA.ttf

S6u9w4BMUTPHh50XSwaPHA.ttf

139 ms

ElegantIcons.woff

ElegantIcons.woff

778 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl1RMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl1RMB.ttf

138 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl1RMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl1RMB.ttf

121 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl1RMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl1RMB.ttf

138 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml1RMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml1RMB.ttf

118 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl1RMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl1RMB.ttf

139 ms

500x400.jpg

500x400.jpg

778 ms

Premium-Collection-slider-new-300x300.jpg

Premium-Collection-slider-new-300x300.jpg

835 ms

amber-slider-new-300x300.jpg

amber-slider-new-300x300.jpg

847 ms

Cloud-slider-new-300x300.jpg

Cloud-slider-new-300x300.jpg

847 ms

Icons.jpg

Icons.jpg

975 ms

Icons2.jpg

Icons2.jpg

996 ms

TMY-1.png

TMY-1.png

1301 ms

More-than-Just-a-Mattress-backdrop.jpg

More-than-Just-a-Mattress-backdrop.jpg

1526 ms

Napure-Collection_pic-1-V2.jpg

Napure-Collection_pic-1-V2.jpg

1297 ms

Napure-Collection_pic-2-V2-e1582098629885.jpg

Napure-Collection_pic-2-V2-e1582098629885.jpg

1075 ms

Napure-Blog-backdrop-1.jpg

Napure-Blog-backdrop-1.jpg

1178 ms

IMG_0627-3.jpg

IMG_0627-3.jpg

1459 ms

IMG_0231-3.jpg

IMG_0231-3.jpg

1330 ms

20190823-lsk-mbr-695.jpg

20190823-lsk-mbr-695.jpg

1903 ms

Blog_6.jpg

Blog_6.jpg

1521 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1550 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1556 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1764 ms

recaptcha__en.js

recaptcha__en.js

22 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

1156 ms

revolution.extension.actions.min.js

revolution.extension.actions.min.js

1160 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

1249 ms

anchor

anchor

31 ms

styles__ltr.css

styles__ltr.css

3 ms

recaptcha__en.js

recaptcha__en.js

10 ms

sr2BvsM2R_OZKHX83mSXJ8YBPDmTxOV2dVCuSpL6Gdo.js

sr2BvsM2R_OZKHX83mSXJ8YBPDmTxOV2dVCuSpL6Gdo.js

33 ms

webworker.js

webworker.js

62 ms

logo_48.png

logo_48.png

22 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

56 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

56 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

55 ms

recaptcha__en.js

recaptcha__en.js

54 ms

loader.gif

loader.gif

243 ms

Accessibility Review

napure.com accessibility score

69

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

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

Heading elements are not in a sequentially-descending order

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

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

napure.com SEO score

93

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

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

napure.com

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