Tools & Wizards About Us
royaltrader.net screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

royaltrader.net

Royal Traders

Page Load Speed

6.6 sec in total

First Response

479 ms

Resources Loaded

5.6 sec

Page Rendered

592 ms

royaltrader.net screenshot

About Website

Visit royaltrader.net now to see the best up-to-date Royal Trader content and also check out these interesting facts you probably never knew about royaltrader.net

Visit royaltrader.net

Key Findings

We analyzed Royaltrader.net page load time and found that the first response time was 479 ms and then it took 6.2 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

royaltrader.net performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value2,710 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

royaltrader.net

479 ms

royaltrader.net

2200 ms

wp-emoji-release.min.js

573 ms

main.css

582 ms

style.min.css

586 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 92% of them (56 requests) were addressed to the original Royaltrader.net, 3% (2 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Royaltrader.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 418.5 kB (13%)

Content Size

3.3 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royaltrader.net main page is 3.3 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. 40% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 144.6 kB

  • Original 183.8 kB
  • After minification 178.1 kB
  • After compression 39.2 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 144.6 kB or 79% of the original size.

Image Optimization

-10%

Potential reduce by 271.8 kB

  • Original 2.7 MB
  • After minification 2.4 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. Royal Trader images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.3 kB

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

CSS Optimization

-1%

Potential reduce by 790 B

  • Original 83.4 kB
  • After minification 83.4 kB
  • After compression 82.6 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. Royaltrader.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

59

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royaltrader.net

royaltrader.net

479 ms

royaltrader.net

royaltrader.net

2200 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

573 ms

main.css

main.css

582 ms

style.min.css

style.min.css

586 ms

classic-themes.min.css

classic-themes.min.css

589 ms

styles.css

styles.css

589 ms

public.css

public.css

594 ms

blocks.css

blocks.css

768 ms

elementor-icons.min.css

elementor-icons.min.css

774 ms

frontend-lite.min.css

frontend-lite.min.css

781 ms

swiper.min.css

swiper.min.css

780 ms

post-3232.css

post-3232.css

784 ms

global.css

global.css

792 ms

post-3193.css

post-3193.css

972 ms

css2

css2

24 ms

style.min.css

style.min.css

1163 ms

css

css

35 ms

jquery.min.js

jquery.min.js

1296 ms

jquery-migrate.min.js

jquery-migrate.min.js

974 ms

widget-icon-box.min.css

widget-icon-box.min.css

810 ms

counter.css

counter.css

734 ms

animations.min.css

animations.min.css

807 ms

app.js

app.js

806 ms

imagesloaded.min.js

imagesloaded.min.js

808 ms

masonry.min.js

masonry.min.js

1029 ms

index.js

index.js

1029 ms

index.js

index.js

1030 ms

events.js

events.js

1030 ms

public.js

public.js

1030 ms

postsTab.js

postsTab.js

1123 ms

api.js

api.js

69 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1136 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1186 ms

wp-polyfill.min.js

wp-polyfill.min.js

1195 ms

index.js

index.js

1201 ms

main.js

main.js

1397 ms

jquery-numerator.min.js

jquery-numerator.min.js

1318 ms

waypoints.min.js

waypoints.min.js

1333 ms

counter.js

counter.js

1378 ms

webpack.runtime.min.js

webpack.runtime.min.js

1390 ms

frontend-modules.min.js

frontend-modules.min.js

1198 ms

core.min.js

core.min.js

1306 ms

frontend.min.js

frontend.min.js

1328 ms

underscore.min.js

underscore.min.js

1358 ms

wp-util.min.js

wp-util.min.js

1371 ms

frontend.min.js

frontend.min.js

1374 ms

1af59774-8433-4a7b-b248-a10ae97f461e.jpg

1af59774-8433-4a7b-b248-a10ae97f461e.jpg

997 ms

handshake_190617.jpg

handshake_190617.jpg

1110 ms

wheat-1.jpg

wheat-1.jpg

1736 ms

Spices-1.jpg

Spices-1.jpg

1355 ms

onion.jpg

onion.jpg

1374 ms

rice-2-1.jpg

rice-2-1.jpg

1593 ms

pulses.png

pulses.png

1783 ms

Red-Chilli.png

Red-Chilli.png

1893 ms

Poly.png

Poly.png

1564 ms

Poly1.png

Poly1.png

1570 ms

unsplash_2vPGGOU-wLA.jpg

unsplash_2vPGGOU-wLA.jpg

1757 ms

1af59774-8433-4a7b-b248-a10ae97f461e-2-1024x643.jpg

1af59774-8433-4a7b-b248-a10ae97f461e-2-1024x643.jpg

1765 ms

font

font

15 ms

recaptcha__en.js

recaptcha__en.js

21 ms

Accessibility Review

royaltrader.net accessibility score

97

Accessibility Issues

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.

Best Practices

royaltrader.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

royaltrader.net SEO score

93

Search Engine Optimization Advices

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 Royaltrader.net 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 Royaltrader.net 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

royaltrader.net

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