Tools & Wizards About Us
royalroses.nl screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

royalroses.nl

Master Growers Of Love | Red Naomi | The Natural Professional | Growers of Love

Page Load Speed

2.7 sec in total

First Response

87 ms

Resources Loaded

2.6 sec

Page Rendered

88 ms

royalroses.nl screenshot

About Website

Welcome to royalroses.nl homepage info - get ready to check Royalroses best content right away, or after learning these important things about royalroses.nl

For many years we are growing the beautiful red rose ‘Red Naomi’ under our brand ‘Royal Roses’. Since 2018 you can also buy our Hydrangea cut flowers.

Visit royalroses.nl

Key Findings

We analyzed Royalroses.nl page load time and found that the first response time was 87 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

royalroses.nl performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

royalroses.nl

87 ms

royalroses.nl

145 ms

1896 ms

bootstrap.css

54 ms

shortcodes.css

79 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 54% of them (37 requests) were addressed to the original Royalroses.nl, 35% (24 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Royalroses.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.9 kB (44%)

Content Size

478.8 kB

After Optimization

266.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royalroses.nl main page is 478.8 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. 60% of websites need less resources to load. CSS take 214.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 95.0 kB

  • Original 121.2 kB
  • After minification 118.1 kB
  • After compression 26.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 95.0 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 4.4 kB

  • Original 46.9 kB
  • After minification 42.5 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. Royalroses images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 6.0 kB

  • Original 95.8 kB
  • After minification 95.8 kB
  • After compression 89.8 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

-50%

Potential reduce by 106.5 kB

  • Original 214.9 kB
  • After minification 214.7 kB
  • After compression 108.4 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. Royalroses.nl needs all CSS files to be minified and compressed as it can save up to 106.5 kB or 50% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (85%)

Requests Now

40

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalroses.nl

royalroses.nl

87 ms

royalroses.nl

royalroses.nl

145 ms

1896 ms

bootstrap.css

bootstrap.css

54 ms

shortcodes.css

shortcodes.css

79 ms

style.min.css

style.min.css

111 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

82 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

90 ms

backTop.css

backTop.css

90 ms

css

css

37 ms

header-left-aligned.css

header-left-aligned.css

90 ms

otb-font-awesome.css

otb-font-awesome.css

106 ms

font-awesome.min.css

font-awesome.min.css

115 ms

style.css

style.css

146 ms

instagram.min.css

instagram.min.css

118 ms

css

css

57 ms

social-logos.min.css

social-logos.min.css

120 ms

jetpack.css

jetpack.css

135 ms

jquery.min.js

jquery.min.js

167 ms

jquery-migrate.min.js

jquery-migrate.min.js

143 ms

bootstrap.js

bootstrap.js

166 ms

init.js

init.js

166 ms

jquery.backTop.min.js

jquery.backTop.min.js

191 ms

navigation.js

navigation.js

176 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

191 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

190 ms

jquery.color.min.js

jquery.color.min.js

194 ms

jquery.fittext.min.js

jquery.fittext.min.js

196 ms

jquery.fitbutton.min.js

jquery.fitbutton.min.js

195 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

196 ms

custom.js

custom.js

197 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

197 ms

eu-cookie-law.min.js

eu-cookie-law.min.js

202 ms

e-202422.js

e-202422.js

17 ms

jetpack-carousel.min.js

jetpack-carousel.min.js

271 ms

google-translate.min.js

google-translate.min.js

272 ms

element.js

element.js

48 ms

gtm.js

gtm.js

139 ms

cropped-RoyalRosesLogoGoldTrans200-1.png

cropped-RoyalRosesLogoGoldTrans200-1.png

193 ms

RoyalRosesLogoGoldTrans200.png

RoyalRosesLogoGoldTrans200.png

123 ms

RoyalRosesLogoGoldTrans300.png

RoyalRosesLogoGoldTrans300.png

230 ms

92 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

63 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

80 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

90 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

93 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

91 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

91 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

90 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

89 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

95 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

94 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

129 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

126 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

127 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

127 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

129 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

130 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

130 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

130 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

131 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

130 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff

132 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff

133 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff

132 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff

133 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

90 ms

uparr-48-w.png

uparr-48-w.png

29 ms

Accessibility Review

royalroses.nl accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

royalroses.nl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

royalroses.nl SEO score

93

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

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 Royalroses.nl 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 Royalroses.nl 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

royalroses.nl

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