Tools & Wizards About Us
royaloxylife.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

royaloxylife.com

Royal Oxylife – RO | UV | UF Water Purifier

Page Load Speed

4.1 sec in total

First Response

493 ms

Resources Loaded

3.4 sec

Page Rendered

158 ms

royaloxylife.com screenshot

About Website

Welcome to royaloxylife.com homepage info - get ready to check Royal Oxylife best content for India right away, or after learning these important things about royaloxylife.com

Ro Water System Manufacturers - Royal Oxylife Suppliers of Commercial Reverse Osmosis System, Ro Water System Manufacturing, Domestic Reverse Osmosis System Manufacturer,Ro Water System Suppliers

Visit royaloxylife.com

Key Findings

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

Performance Metrics

royaloxylife.com performance score

0

Network Requests Diagram

royaloxylife.com

493 ms

www.royaloxylife.com

491 ms

common.css

12 ms

styles.css

30 ms

header.css

17 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Royaloxylife.com, 78% (50 requests) were made to Catalog.wlimg.com and 8% (5 requests) were made to Catalog.weblink.in. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Catalog.wlimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.7 kB (31%)

Content Size

622.3 kB

After Optimization

426.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royaloxylife.com main page is 622.3 kB. 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. Javascripts take 372.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 26.2 kB

  • Original 34.9 kB
  • After minification 34.1 kB
  • After compression 8.6 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 26.2 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 4.6 kB

  • Original 164.7 kB
  • After minification 160.1 kB

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. Royal Oxylife images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 138.8 kB

  • Original 372.5 kB
  • After minification 357.1 kB
  • After compression 233.7 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 138.8 kB or 37% of the original size.

CSS Optimization

-52%

Potential reduce by 26.0 kB

  • Original 50.3 kB
  • After minification 43.7 kB
  • After compression 24.3 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. Royaloxylife.com needs all CSS files to be minified and compressed as it can save up to 26.0 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (77%)

Requests Now

62

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royaloxylife.com

royaloxylife.com

493 ms

www.royaloxylife.com

www.royaloxylife.com

491 ms

common.css

common.css

12 ms

styles.css

styles.css

30 ms

header.css

header.css

17 ms

elements.css

elements.css

17 ms

footer.css

footer.css

18 ms

carousel_dg.css

carousel_dg.css

18 ms

jquery.tabs.css

jquery.tabs.css

31 ms

nivo-slider.css

nivo-slider.css

23 ms

theme-blue-gray-white.css

theme-blue-gray-white.css

19 ms

jquery-ui.css

jquery-ui.css

20 ms

jquery.fancybox.css

jquery.fancybox.css

23 ms

3240045.css

3240045.css

441 ms

jquery.latest.min.js

jquery.latest.min.js

24 ms

bizcatglog-js.js

bizcatglog-js.js

25 ms

country_list.js

country_list.js

25 ms

common-static-form.js

common-static-form.js

25 ms

swfobject-new.js

swfobject-new.js

26 ms

jquery-ui.min.js

jquery-ui.min.js

32 ms

common.js

common.js

27 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

32 ms

lib.min.js

lib.min.js

28 ms

jcarousellite_1.0.dg.js

jcarousellite_1.0.dg.js

37 ms

ddsmoothmenu.js

ddsmoothmenu.js

28 ms

jquery.easing.latest.js

jquery.easing.latest.js

30 ms

jquery.DG_Slider.min.js

jquery.DG_Slider.min.js

34 ms

scroll.js

scroll.js

31 ms

12312.js

12312.js

32 ms

jquery.ui.totop.js

jquery.ui.totop.js

38 ms

project.js

project.js

39 ms

PIE.js

PIE.js

32 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

33 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

34 ms

jquery.mousewheel.pack.js

jquery.mousewheel.pack.js

35 ms

jquery.photo.gallery.js

jquery.photo.gallery.js

35 ms

jquery.paging.photo.gallery.js

jquery.paging.photo.gallery.js

35 ms

gtranslate.js

gtranslate.js

35 ms

index.php

index.php

480 ms

translateelement.css

translateelement.css

4 ms

main.js

main.js

72 ms

commercial-reverse-osmosis-system-1413358.jpg

commercial-reverse-osmosis-system-1413358.jpg

491 ms

domestic-reverse-osmosis-system-1413357.jpg

domestic-reverse-osmosis-system-1413357.jpg

456 ms

12312-comp-image.png

12312-comp-image.png

1358 ms

sprite.png

sprite.png

31 ms

61676.jpg

61676.jpg

1209 ms

63676.jpg

63676.jpg

1923 ms

fi-24x16.png

fi-24x16.png

29 ms

fr-24x16.png

fr-24x16.png

30 ms

el-24x16.png

el-24x16.png

51 ms

hi-24x16.png

hi-24x16.png

29 ms

rss_icon.png

rss_icon.png

29 ms

common_x_bgs_50px.png

common_x_bgs_50px.png

22 ms

headerShadow.png

headerShadow.png

22 ms

webfont.ttf

webfont.ttf

34 ms

input_bg.png

input_bg.png

25 ms

black_format1_2.gif

black_format1_2.gif

440 ms

scroll-t.png

scroll-t.png

25 ms

black_format1_4.gif

black_format1_4.gif

440 ms

black_format1_7.gif

black_format1_7.gif

443 ms

element_main.js

element_main.js

39 ms

translate_24dp.png

translate_24dp.png

28 ms

l

l

48 ms

googlelogo_color_42x16dp.png

googlelogo_color_42x16dp.png

21 ms

SEO Factors

royaloxylife.com SEO score

0

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

royaloxylife.com

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