Tools & Wizards About Us
royalfamily.org 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

royalfamily.org

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

Page Load Speed

4.4 sec in total

First Response

57 ms

Resources Loaded

4 sec

Page Rendered

342 ms

royalfamily.org screenshot

About Website

Visit royalfamily.org now to see the best up-to-date Royal Family content for Serbia and also check out these interesting facts you probably never knew about royalfamily.org

Royal Family See more History of the Dynasty See more Family tree See more

Visit royalfamily.org

Key Findings

We analyzed Royalfamily.org page load time and found that the first response time was 57 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

royalfamily.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value4,350 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

royalfamily.org

57 ms

royalfamily.org

1502 ms

layerslider.css

395 ms

fontawesome-all.css

373 ms

frontend.css

380 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 94% of them (104 requests) were addressed to the original Royalfamily.org, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Royalfamily.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 341.8 kB (12%)

Content Size

2.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royalfamily.org main page is 2.8 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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 130.0 kB

  • Original 158.2 kB
  • After minification 153.7 kB
  • After compression 28.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 130.0 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 177.3 kB

  • Original 2.0 MB
  • After minification 1.9 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 Family images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 33.0 kB

  • Original 392.8 kB
  • After minification 392.8 kB
  • After compression 359.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.5 kB

  • Original 223.8 kB
  • After minification 223.8 kB
  • After compression 222.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. Royalfamily.org 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 Family. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 75 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

royalfamily.org

royalfamily.org

57 ms

royalfamily.org

royalfamily.org

1502 ms

layerslider.css

layerslider.css

395 ms

fontawesome-all.css

fontawesome-all.css

373 ms

frontend.css

frontend.css

380 ms

style.min.css

style.min.css

25 ms

1a79a8faa579ce18c3f1cd41864f0c7f.min.css

1a79a8faa579ce18c3f1cd41864f0c7f.min.css

83 ms

jquery.min.js

jquery.min.js

41 ms

jquery-migrate.min.js

jquery-migrate.min.js

55 ms

layerslider.utils.js

layerslider.utils.js

74 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

139 ms

layerslider.transitions.js

layerslider.transitions.js

138 ms

script.js

script.js

135 ms

js

js

46 ms

api.js

api.js

80 ms

style.min.css

style.min.css

62 ms

socialsnap.css

socialsnap.css

81 ms

index.js

index.js

77 ms

index.js

index.js

82 ms

api.js

api.js

103 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

87 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

107 ms

wp-polyfill.min.js

wp-polyfill.min.js

567 ms

index.js

index.js

97 ms

awb-tabs-widget.js

awb-tabs-widget.js

108 ms

awb-vertical-menu-widget.js

awb-vertical-menu-widget.js

126 ms

cssua.js

cssua.js

122 ms

modernizr.js

modernizr.js

132 ms

fusion.js

fusion.js

138 ms

isotope.js

isotope.js

146 ms

packery.js

packery.js

151 ms

swiper.js

swiper.js

162 ms

bootstrap.transition.js

bootstrap.transition.js

166 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

174 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

180 ms

jquery.easing.js

jquery.easing.js

188 ms

jquery.fitvids.js

jquery.fitvids.js

192 ms

jquery.flexslider.js

jquery.flexslider.js

199 ms

jquery.ilightbox.js

jquery.ilightbox.js

212 ms

jquery.infinitescroll.js

jquery.infinitescroll.js

212 ms

jquery.mousewheel.js

jquery.mousewheel.js

225 ms

jquery.placeholder.js

jquery.placeholder.js

224 ms

jquery.fade.js

jquery.fade.js

241 ms

imagesLoaded.js

imagesLoaded.js

245 ms

fusion-equal-heights.js

fusion-equal-heights.js

200 ms

fusion-parallax.js

fusion-parallax.js

206 ms

fusion-video-general.js

fusion-video-general.js

209 ms

fusion-video-bg.js

fusion-video-bg.js

215 ms

fusion-lightbox.js

fusion-lightbox.js

220 ms

fusion-tooltip.js

fusion-tooltip.js

228 ms

fusion-sharing-box.js

fusion-sharing-box.js

216 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

226 ms

fusion-youtube.js

fusion-youtube.js

223 ms

vimeoPlayer.js

vimeoPlayer.js

220 ms

avada-general-footer.js

avada-general-footer.js

573 ms

avada-quantity.js

avada-quantity.js

268 ms

avada-crossfade-images.js

avada-crossfade-images.js

268 ms

avada-select.js

avada-select.js

255 ms

avada-wpml.js

avada-wpml.js

251 ms

avada-contact-form-7.js

avada-contact-form-7.js

245 ms

avada-privacy.js

avada-privacy.js

240 ms

avada-live-search.js

avada-live-search.js

237 ms

fusion-alert.js

fusion-alert.js

228 ms

awb-off-canvas.js

awb-off-canvas.js

219 ms

fusion-flexslider.js

fusion-flexslider.js

218 ms

fusion-animations.js

fusion-animations.js

208 ms

fusion-column-legacy.js

fusion-column-legacy.js

204 ms

awb-background-slider.js

awb-background-slider.js

197 ms

fusion-blog.js

fusion-blog.js

192 ms

fusion-container.js

fusion-container.js

185 ms

avada-drop-down.js

avada-drop-down.js

173 ms

avada-to-top.js

avada-to-top.js

173 ms

avada-header.js

avada-header.js

162 ms

avada-menu.js

avada-menu.js

209 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

194 ms

avada-scrollspy.js

avada-scrollspy.js

190 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

474 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

176 ms

fusion-general-global.js

fusion-general-global.js

173 ms

fusion-video.js

fusion-video.js

163 ms

fusion-column.js

fusion-column.js

158 ms

socialsnap.js

socialsnap.js

468 ms

logo-vector-02.png

logo-vector-02.png

67 ms

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

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

68 ms

Bedz-A2-plavi.jpg

Bedz-A2-plavi.jpg

68 ms

COVER-PA.jpg

COVER-PA.jpg

838 ms

COVER-rucak-za-episkope-SPC-2024.jpg

COVER-rucak-za-episkope-SPC-2024.jpg

901 ms

COVER-Indjija.jpg

COVER-Indjija.jpg

1019 ms

COVER-TOB-2024.jpg

COVER-TOB-2024.jpg

853 ms

KS-logo-boja-PNG-e1580398507731.png

KS-logo-boja-PNG-e1580398507731.png

368 ms

artnajnoviji.png

artnajnoviji.png

717 ms

rsz_coca_cola_hbc_logo.png

rsz_coca_cola_hbc_logo.png

488 ms

maruskanajnovije.png

maruskanajnovije.png

750 ms

Vinarija-PIK-OPLENAC.jpg

Vinarija-PIK-OPLENAC.jpg

1064 ms

MTS_logobig.png

MTS_logobig.png

1407 ms

Mercedes-Benz-Logo.svg.png

Mercedes-Benz-Logo.svg.png

839 ms

TOS-eng.png

TOS-eng.png

853 ms

BMW_logo.png

BMW_logo.png

1620 ms

js

js

67 ms

analytics.js

analytics.js

63 ms

MyriadPro-Regular.otf

MyriadPro-Regular.otf

800 ms

fa-brands-400.woff

fa-brands-400.woff

1429 ms

fa-brands-400.woff

fa-brands-400.woff

1404 ms

MyriadPro-Bold.otf

MyriadPro-Bold.otf

1540 ms

awb-icons.woff

awb-icons.woff

1003 ms

fa-solid-900.woff

fa-solid-900.woff

1674 ms

fa-solid-900.woff

fa-solid-900.woff

1916 ms

fa-regular-400.woff

fa-regular-400.woff

1871 ms

fa-regular-400.woff

fa-regular-400.woff

1884 ms

collect

collect

99 ms

collect

collect

27 ms

Accessibility Review

royalfamily.org 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

royalfamily.org 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

royalfamily.org 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 Royalfamily.org 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 Royalfamily.org 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

royalfamily.org

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