Tools & Wizards About Us
royalperde.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

royalperde.com

Royal Perde Sistemleri | Ev ve Ofis Perdeleri Üretimi Ve Uygulamaları

Page Load Speed

5.1 sec in total

First Response

293 ms

Resources Loaded

4.2 sec

Page Rendered

567 ms

royalperde.com screenshot

About Website

Click here to check amazing Royal Perde content for Turkey. Otherwise, check out these important facts you probably never knew about royalperde.com

Perde çeşitleri, stor perde, akustik perde, dikey perde, jaluzi, ahşap perde, sun screen perde, zebra perde, kumaş ve tül, karartma perde, motorlu perdeler, sahne-projeksiyon perdesi üretimi.

Visit royalperde.com

Key Findings

We analyzed Royalperde.com page load time and found that the first response time was 293 ms and then it took 4.8 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

royalperde.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value27.2 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

royalperde.com

293 ms

www.royalperde.com

1585 ms

js.js

94 ms

jquery-1.8.3.min.jgz

278 ms

jquery.bxslider.min.js

288 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 97% of them (87 requests) were addressed to the original Royalperde.com, 3% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Royalperde.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 385.9 kB (6%)

Content Size

6.1 MB

After Optimization

5.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royalperde.com main page is 6.1 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. 60% of websites need less resources to load. Images take 5.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 74.8 kB

  • Original 92.8 kB
  • After minification 90.4 kB
  • After compression 18.0 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 74.8 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 300.3 kB

  • Original 5.9 MB
  • After minification 5.6 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 Perde images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 7.2 kB

  • Original 78.0 kB
  • After minification 78.0 kB
  • After compression 70.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

-12%

Potential reduce by 3.6 kB

  • Original 29.7 kB
  • After minification 29.7 kB
  • After compression 26.2 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. Royalperde.com needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (28%)

Requests Now

87

After Optimization

63

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalperde.com

royalperde.com

293 ms

www.royalperde.com

www.royalperde.com

1585 ms

js.js

js.js

94 ms

jquery-1.8.3.min.jgz

jquery-1.8.3.min.jgz

278 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

288 ms

jquery.bxslider.css

jquery.bxslider.css

288 ms

magnific-popup.css

magnific-popup.css

289 ms

wookmark-main.css

wookmark-main.css

289 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

290 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

371 ms

wookmark.js

wookmark.js

372 ms

banner-rotator.min.css

banner-rotator.min.css

373 ms

jquery.banner-rotator.min.js

jquery.banner-rotator.min.js

466 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

376 ms

page.js

page.js

37 ms

grid.css

grid.css

94 ms

stil.css

stil.css

95 ms

desktop.css

desktop.css

98 ms

mobile.css

mobile.css

96 ms

bg.png

bg.png

93 ms

homepage.png

homepage.png

94 ms

favorite.png

favorite.png

94 ms

sitemap.png

sitemap.png

94 ms

search-glass.png

search-glass.png

95 ms

facebook.png

facebook.png

96 ms

whatsapp.png

whatsapp.png

185 ms

twitter.png

twitter.png

186 ms

instagram.png

instagram.png

184 ms

youtube.png

youtube.png

186 ms

logo.png

logo.png

280 ms

en_yeni_baslik.png

en_yeni_baslik.png

189 ms

en_yeni_iletisim.png

en_yeni_iletisim.png

465 ms

logo-2.png

logo-2.png

375 ms

ep1016325_20210812181945.jpg

ep1016325_20210812181945.jpg

748 ms

ep1016325_20210725025153.png

ep1016325_20210725025153.png

749 ms

ep1016325_20210725025315.png

ep1016325_20210725025315.png

750 ms

ep1016325_20210812175415.png

ep1016325_20210812175415.png

652 ms

ep1016325_20210725025344.png

ep1016325_20210725025344.png

657 ms

ep1016325_20210812180935.png

ep1016325_20210812180935.png

1111 ms

ep1016325_20210823021733.jpg

ep1016325_20210823021733.jpg

933 ms

182141.jpg

182141.jpg

754 ms

210325.jpg

210325.jpg

854 ms

210326.jpg

210326.jpg

844 ms

210329.jpg

210329.jpg

845 ms

210324.jpg

210324.jpg

849 ms

182139.jpg

182139.jpg

939 ms

182138.jpg

182138.jpg

941 ms

210332.jpg

210332.jpg

943 ms

210328.jpg

210328.jpg

949 ms

210327.jpg

210327.jpg

1027 ms

210331.jpg

210331.jpg

1034 ms

210330.jpg

210330.jpg

1036 ms

karartma_stor_perde.jpg

karartma_stor_perde.jpg

1038 ms

karartma_perdeler_(16).jpg

karartma_perdeler_(16).jpg

1045 ms

25_mm_ah_ap_jaluz_.jpg

25_mm_ah_ap_jaluz_.jpg

1114 ms

default.css

default.css

1037 ms

katlamali_perde_mekanizmasi.jpg

katlamali_perde_mekanizmasi.jpg

1134 ms

stor_perde_plastik_portray_2.jpg

stor_perde_plastik_portray_2.jpg

1135 ms

urun_2.jpg

urun_2.jpg

1134 ms

partners.png

partners.png

1149 ms

52889498.jpg

52889498.jpg

1148 ms

52872542.jpg

52872542.jpg

1059 ms

52745261.jpg

52745261.jpg

1062 ms

51774968.jpg

51774968.jpg

1060 ms

51102485.jpg

51102485.jpg

1061 ms

52308539.jpg

52308539.jpg

1298 ms

51300769.jpg

51300769.jpg

1036 ms

50284320.jpg

50284320.jpg

944 ms

50284560.jpg

50284560.jpg

865 ms

52092586.jpg

52092586.jpg

679 ms

51775100.jpg

51775100.jpg

677 ms

51775160.jpg

51775160.jpg

663 ms

pagination_next.png

pagination_next.png

662 ms

motorlu_stor_perde.jpg

motorlu_stor_perde.jpg

676 ms

islemeli_stor_perde_royal_modeli.jpg

islemeli_stor_perde_royal_modeli.jpg

674 ms

katlamali_perde_8.jpg

katlamali_perde_8.jpg

587 ms

akustik_bostanci.jpg

akustik_bostanci.jpg

662 ms

plise_perde_(54).jpg

plise_perde_(54).jpg

659 ms

kis-bahcesi-perde.jpg

kis-bahcesi-perde.jpg

668 ms

hastane_perdeleri.jpg

hastane_perdeleri.jpg

591 ms

karo-hali-doseme.jpg2.jpg

karo-hali-doseme.jpg2.jpg

587 ms

mineflo_yer_dosemesi.jpg

mineflo_yer_dosemesi.jpg

640 ms

duvar_kagidi.jpg

duvar_kagidi.jpg

659 ms

icon-sf3d4f583f7.png

icon-sf3d4f583f7.png

383 ms

spacer.png

spacer.png

396 ms

arrow.png

arrow.png

392 ms

desktop_grid.css

desktop_grid.css

377 ms

mobile_grid.css

mobile_grid.css

432 ms

sm.25.html

sm.25.html

17 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

31 ms

Accessibility Review

royalperde.com accessibility score

68

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

royalperde.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

royalperde.com SEO score

90

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

Image elements do not have [alt] attributes

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

    TR

  • Language Claimed

    TR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalperde.com can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and it matches the claimed language. Our system also found out that Royalperde.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

royalperde.com

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