Tools & Wizards About Us
royalmetros.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

royalmetros.com

Universal Kitchen LTD – Building A Better Kitchen

Page Load Speed

9.7 sec in total

First Response

2.6 sec

Resources Loaded

6.6 sec

Page Rendered

461 ms

royalmetros.com screenshot

About Website

Click here to check amazing Royalmetros content for Nigeria. Otherwise, check out these important facts you probably never knew about royalmetros.com

Visit royalmetros.com

Key Findings

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

Performance Metrics

royalmetros.com performance score

0

Network Requests Diagram

royalmetros.com

2620 ms

main.min.css

364 ms

css

48 ms

style.min.css

239 ms

view.css

299 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 85% of them (57 requests) were addressed to the original Royalmetros.com, 4% (3 requests) were made to Stats.wp.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Royalmetros.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.9 kB (14%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royalmetros.com main page is 1.2 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 729.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 163.8 kB

  • Original 197.1 kB
  • After minification 193.7 kB
  • After compression 33.3 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 163.8 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 10.3 kB

  • Original 729.5 kB
  • After minification 719.2 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. Royalmetros images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 220 B

  • Original 153.4 kB
  • After minification 153.4 kB
  • After compression 153.1 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

-0%

Potential reduce by 556 B

  • Original 150.5 kB
  • After minification 150.5 kB
  • After compression 150.0 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. Royalmetros.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

60

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalmetros.com

royalmetros.com

2620 ms

main.min.css

main.min.css

364 ms

css

css

48 ms

style.min.css

style.min.css

239 ms

view.css

view.css

299 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

290 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

334 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

535 ms

wc-blocks-style.css

wc-blocks-style.css

559 ms

woocommerce-layout-grid.min.css

woocommerce-layout-grid.min.css

612 ms

woocommerce-grid.min.css

woocommerce-grid.min.css

637 ms

elementor-icons.min.css

elementor-icons.min.css

615 ms

frontend-lite.min.css

frontend-lite.min.css

676 ms

swiper.min.css

swiper.min.css

659 ms

post-3049.css

post-3049.css

644 ms

all.min.css

all.min.css

683 ms

v4-shims.min.css

v4-shims.min.css

687 ms

post-95.css

post-95.css

694 ms

css

css

43 ms

fontawesome.min.css

fontawesome.min.css

696 ms

solid.min.css

solid.min.css

687 ms

regular.min.css

regular.min.css

712 ms

jetpack.css

jetpack.css

704 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

702 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

727 ms

wp-polyfill.min.js

wp-polyfill.min.js

749 ms

hooks.min.js

hooks.min.js

815 ms

w.js

w.js

29 ms

jquery.min.js

jquery.min.js

908 ms

jquery-migrate.min.js

jquery-migrate.min.js

925 ms

s-202403.js

s-202403.js

29 ms

v4-shims.min.js

v4-shims.min.js

943 ms

g.gif

g.gif

14 ms

Universal-Kitchen-Ltd.png

Universal-Kitchen-Ltd.png

28 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

27 ms

ukl.png

ukl.png

92 ms

ukl-1.jpg

ukl-1.jpg

70 ms

widget-icon-box.min.css

widget-icon-box.min.css

147 ms

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

4 ms

fa-solid-900.woff

fa-solid-900.woff

186 ms

fa-regular-400.woff

fa-regular-400.woff

175 ms

Universal-Kitchen-Ltd-1.png

Universal-Kitchen-Ltd-1.png

207 ms

animations.min.css

animations.min.css

301 ms

frontend.min.js

frontend.min.js

211 ms

mobile-cart.min.js

mobile-cart.min.js

262 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

430 ms

add-to-cart.min.js

add-to-cart.min.js

478 ms

js.cookie.min.js

js.cookie.min.js

506 ms

woocommerce.min.js

woocommerce.min.js

512 ms

e-202403.js

e-202403.js

2 ms

cart-fragments.min.js

cart-fragments.min.js

515 ms

webpack.runtime.min.js

webpack.runtime.min.js

532 ms

frontend-modules.min.js

frontend-modules.min.js

577 ms

waypoints.min.js

waypoints.min.js

580 ms

core.min.js

core.min.js

604 ms

frontend.min.js

frontend.min.js

607 ms

underscore.min.js

underscore.min.js

612 ms

wp-util.min.js

wp-util.min.js

631 ms

frontend.min.js

frontend.min.js

673 ms

ukl.jpg

ukl.jpg

772 ms

Ba.jpg

Ba.jpg

651 ms

ukl-3.jpg

ukl-3.jpg

689 ms

eicons.woff

eicons.woff

734 ms

g.gif

g.gif

5 ms

royalmetros.com

royalmetros.com

443 ms

woocommerce-smallscreen-grid.min.css

woocommerce-smallscreen-grid.min.css

33 ms

SEO Factors

royalmetros.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 Royalmetros.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 Royalmetros.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

royalmetros.com

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