Tools & Wizards About Us
royal.rs screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

royal.rs

The Royal Family of Serbia - From the people, for the people

Page Load Speed

3.5 sec in total

First Response

132 ms

Resources Loaded

3 sec

Page Rendered

356 ms

royal.rs screenshot

About Website

Welcome to royal.rs homepage info - get ready to check Royal best content right away, or after learning these important things about royal.rs

The Royal Family of Serbia – From the people, for the people. History and current events of the Royal Family of Serbia.

Visit royal.rs

Key Findings

We analyzed Royal.rs page load time and found that the first response time was 132 ms and then it took 3.4 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

royal.rs performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.088

93/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

royal.rs

132 ms

royalfamily.org

430 ms

layerslider.css

18 ms

fontawesome-all.css

23 ms

frontend.css

40 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Royal.rs, 90% (102 requests) were made to Royalfamily.org and 3% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (692 ms) relates to the external source Royalfamily.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 301.6 kB (11%)

Content Size

2.6 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royal.rs main page is 2.6 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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 135.5 kB

  • Original 166.4 kB
  • After minification 166.3 kB
  • After compression 30.9 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 135.5 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 162.4 kB

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

JavaScript Optimization

-0%

Potential reduce by 2.1 kB

  • Original 576.9 kB
  • After minification 576.9 kB
  • After compression 574.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

-1%

Potential reduce by 1.6 kB

  • Original 225.3 kB
  • After minification 225.3 kB
  • After compression 223.7 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. Royal.rs has all CSS files already compressed.

Requests Breakdown

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

Requests Now

100

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royal.rs

royal.rs

132 ms

royalfamily.org

royalfamily.org

430 ms

layerslider.css

layerslider.css

18 ms

fontawesome-all.css

fontawesome-all.css

23 ms

frontend.css

frontend.css

40 ms

style.min.css

style.min.css

30 ms

495cd0ce1e9d7905c4b9c4400e4b755a.min.css

495cd0ce1e9d7905c4b9c4400e4b755a.min.css

63 ms

jquery.min.js

jquery.min.js

33 ms

jquery-migrate.min.js

jquery-migrate.min.js

26 ms

layerslider.utils.js

layerslider.utils.js

41 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

47 ms

layerslider.transitions.js

layerslider.transitions.js

46 ms

script.js

script.js

47 ms

js

js

55 ms

api.js

api.js

42 ms

style.min.css

style.min.css

53 ms

socialsnap.css

socialsnap.css

51 ms

hooks.min.js

hooks.min.js

212 ms

i18n.min.js

i18n.min.js

55 ms

index.js

index.js

56 ms

index.js

index.js

214 ms

api.js

api.js

215 ms

wp-polyfill.min.js

wp-polyfill.min.js

216 ms

index.js

index.js

215 ms

awb-tabs-widget.js

awb-tabs-widget.js

217 ms

awb-vertical-menu-widget.js

awb-vertical-menu-widget.js

218 ms

cssua.js

cssua.js

219 ms

modernizr.js

modernizr.js

221 ms

fusion.js

fusion.js

314 ms

isotope.js

isotope.js

314 ms

packery.js

packery.js

314 ms

swiper.js

swiper.js

315 ms

bootstrap.transition.js

bootstrap.transition.js

316 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

316 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

317 ms

jquery.easing.js

jquery.easing.js

318 ms

jquery.fitvids.js

jquery.fitvids.js

318 ms

jquery.flexslider.js

jquery.flexslider.js

318 ms

jquery.ilightbox.js

jquery.ilightbox.js

319 ms

jquery.infinitescroll.js

jquery.infinitescroll.js

321 ms

jquery.mousewheel.js

jquery.mousewheel.js

317 ms

jquery.fade.js

jquery.fade.js

310 ms

imagesLoaded.js

imagesLoaded.js

305 ms

fusion-equal-heights.js

fusion-equal-heights.js

300 ms

fusion-parallax.js

fusion-parallax.js

299 ms

fusion-video-general.js

fusion-video-general.js

295 ms

fusion-video-bg.js

fusion-video-bg.js

291 ms

fusion-lightbox.js

fusion-lightbox.js

288 ms

fusion-tooltip.js

fusion-tooltip.js

285 ms

fusion-sharing-box.js

fusion-sharing-box.js

284 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

284 ms

fusion-youtube.js

fusion-youtube.js

279 ms

vimeoPlayer.js

vimeoPlayer.js

277 ms

fusion-general-global.js

fusion-general-global.js

287 ms

avada-general-footer.js

avada-general-footer.js

275 ms

recaptcha__en.js

recaptcha__en.js

212 ms

avada-quantity.js

avada-quantity.js

160 ms

avada-crossfade-images.js

avada-crossfade-images.js

155 ms

avada-select.js

avada-select.js

157 ms

avada-wpml.js

avada-wpml.js

152 ms

avada-contact-form-7.js

avada-contact-form-7.js

153 ms

avada-privacy.js

avada-privacy.js

151 ms

avada-live-search.js

avada-live-search.js

153 ms

fusion-alert.js

fusion-alert.js

60 ms

awb-off-canvas.js

awb-off-canvas.js

60 ms

fusion-flexslider.js

fusion-flexslider.js

60 ms

fusion-animations.js

fusion-animations.js

60 ms

fusion-column-legacy.js

fusion-column-legacy.js

60 ms

awb-background-slider.js

awb-background-slider.js

116 ms

fusion-blog.js

fusion-blog.js

115 ms

fusion-container.js

fusion-container.js

117 ms

avada-drop-down.js

avada-drop-down.js

118 ms

avada-to-top.js

avada-to-top.js

117 ms

avada-header.js

avada-header.js

116 ms

avada-menu.js

avada-menu.js

118 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

117 ms

avada-scrollspy.js

avada-scrollspy.js

117 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

119 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

119 ms

fusion-video.js

fusion-video.js

120 ms

fusion-column.js

fusion-column.js

119 ms

socialsnap.js

socialsnap.js

120 ms

grb-za-SAJT-podlogu-malo-smanjeno.png

grb-za-SAJT-podlogu-malo-smanjeno.png

123 ms

MyriadPro-Regular.otf

MyriadPro-Regular.otf

73 ms

fa-brands-400.woff

fa-brands-400.woff

509 ms

fa-brands-400.woff

fa-brands-400.woff

71 ms

MyriadPro-Bold.otf

MyriadPro-Bold.otf

74 ms

awb-icons.woff

awb-icons.woff

73 ms

fa-solid-900.woff

fa-solid-900.woff

606 ms

fa-solid-900.woff

fa-solid-900.woff

73 ms

fa-regular-400.woff

fa-regular-400.woff

424 ms

fa-regular-400.woff

fa-regular-400.woff

444 ms

fallback

fallback

87 ms

fallback__ltr.css

fallback__ltr.css

14 ms

css

css

33 ms

logo_48.png

logo_48.png

3 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

29 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

35 ms

logo-vector-02.png

logo-vector-02.png

16 ms

Bedz-A2-plavi.jpg

Bedz-A2-plavi.jpg

16 ms

COVER-LL-NY-2024-PA.jpg

COVER-LL-NY-2024-PA.jpg

22 ms

COVER-Ukrajina-skola.jpg

COVER-Ukrajina-skola.jpg

692 ms

COVER-Drustvo-prijatelja-Svetih-Arhangela.jpg

COVER-Drustvo-prijatelja-Svetih-Arhangela.jpg

598 ms

COVER-Rada-Vranjesevic-PA.jpg

COVER-Rada-Vranjesevic-PA.jpg

597 ms

KS-logo-boja-PNG-e1580398507731.png

KS-logo-boja-PNG-e1580398507731.png

20 ms

artnajnoviji.png

artnajnoviji.png

19 ms

rsz_coca_cola_hbc_logo.png

rsz_coca_cola_hbc_logo.png

29 ms

maruskanajnovije.png

maruskanajnovije.png

29 ms

Vinarija-PIK-OPLENAC.jpg

Vinarija-PIK-OPLENAC.jpg

31 ms

MTS_logobig.png

MTS_logobig.png

39 ms

Mercedes-Benz-Logo.svg.png

Mercedes-Benz-Logo.svg.png

37 ms

TOS-eng.png

TOS-eng.png

40 ms

BMW_logo.png

BMW_logo.png

47 ms

Accessibility Review

royal.rs accessibility score

83

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

[lang] attributes do not have a valid value

Best Practices

royal.rs 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

SEO Factors

royal.rs SEO score

76

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

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Royal.rs 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 Royal.rs 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

royal.rs

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