Tools & Wizards About Us
royalpepperbanquets.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

royalpepperbanquets.com

Best Wedding Hall in Wazirpur, Rohini, Peeragarhi, Delhi | India

Page Load Speed

1.3 sec in total

First Response

9 ms

Resources Loaded

940 ms

Page Rendered

389 ms

royalpepperbanquets.com screenshot

About Website

Click here to check amazing Royalpepperbanquets content for India. Otherwise, check out these important facts you probably never knew about royalpepperbanquets.com

Royal Pepper Banquets is a renowned Marriage and Wedding Hall in North Delhi India, providing excellent and luxurious wedding halls, exceptional catering facilities at affordable rates.

Visit royalpepperbanquets.com

Key Findings

We analyzed Royalpepperbanquets.com page load time and found that the first response time was 9 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

royalpepperbanquets.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

royalpepperbanquets.com

9 ms

www.royalpepperbanquets.com

142 ms

bootstrap.min.css

12 ms

navbar.css

38 ms

all.css

91 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 56% of them (37 requests) were addressed to the original Royalpepperbanquets.com, 15% (10 requests) were made to Fonts.gstatic.com and 12% (8 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (502 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (59%)

Content Size

4.1 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royalpepperbanquets.com main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 223.3 kB

  • Original 242.8 kB
  • After minification 155.8 kB
  • After compression 19.4 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. This page needs HTML code to be minified as it can gain 87.0 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 223.3 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 329.0 kB
  • After minification 329.0 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. Royalpepperbanquets images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 1.8 MB

  • Original 3.1 MB
  • After minification 3.1 MB
  • After compression 1.3 MB

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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.8 MB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 380.3 kB

  • Original 459.0 kB
  • After minification 417.3 kB
  • After compression 78.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. Royalpepperbanquets.com needs all CSS files to be minified and compressed as it can save up to 380.3 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalpepperbanquets.com

royalpepperbanquets.com

9 ms

www.royalpepperbanquets.com

www.royalpepperbanquets.com

142 ms

bootstrap.min.css

bootstrap.min.css

12 ms

navbar.css

navbar.css

38 ms

all.css

all.css

91 ms

fontawesome.css

fontawesome.css

96 ms

brands.css

brands.css

77 ms

solid.css

solid.css

70 ms

all.js

all.js

106 ms

slick.min.css

slick.min.css

95 ms

slick-theme.min.css

slick-theme.min.css

133 ms

Unit.css

Unit.css

103 ms

Gallery.css

Gallery.css

142 ms

Feedback.css

Feedback.css

159 ms

style.css

style.css

123 ms

LightGallery.css

LightGallery.css

167 ms

iziToast.min.css

iziToast.min.css

165 ms

iziToast.min.js

iziToast.min.js

159 ms

js

js

136 ms

api.js

api.js

119 ms

js

js

156 ms

brands.js

brands.js

152 ms

solid.js

solid.js

151 ms

fontawesome.js

fontawesome.js

242 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

242 ms

jquery.min.js

jquery.min.js

243 ms

slick.min.js

slick.min.js

349 ms

LightGallery.js

LightGallery.js

349 ms

lg-pager.js

lg-pager.js

136 ms

lg-autoplay.js

lg-autoplay.js

140 ms

lg-share.js

lg-share.js

146 ms

lg-fullscreen.js

lg-fullscreen.js

138 ms

lg-hash.js

lg-hash.js

170 ms

picturefill.min.js

picturefill.min.js

111 ms

custom.js

custom.js

250 ms

css2

css2

35 ms

css2

css2

53 ms

lg-zoom.js

lg-zoom.js

21 ms

lightgallery.js

lightgallery.js

22 ms

lg-pager.js

lg-pager.js

20 ms

lg-fullscreen.js

lg-fullscreen.js

20 ms

lg-autoplay.js

lg-autoplay.js

25 ms

lg-share.js

lg-share.js

18 ms

lg-hash.js

lg-hash.js

69 ms

Lgog.png

Lgog.png

132 ms

17245672881229133865.avif

17245672881229133865.avif

448 ms

17199108742045559095.avif

17199108742045559095.avif

448 ms

blank.jpeg

blank.jpeg

431 ms

KFOmCnqEu92Fr1Me5mZNCzc.woff

KFOmCnqEu92Fr1Me5mZNCzc.woff

132 ms

KFOlCnqEu92Fr1MmEU9vAB0_IsE.woff

KFOlCnqEu92Fr1MmEU9vAB0_IsE.woff

431 ms

KFOlCnqEu92Fr1MmSU5vAB0_IsE.woff

KFOlCnqEu92Fr1MmSU5vAB0_IsE.woff

502 ms

KFOkCnqEu92Fr1MmgWxMKTU1Kg.woff

KFOkCnqEu92Fr1MmgWxMKTU1Kg.woff

502 ms

KFOlCnqEu92Fr1MmWUlvAB0_IsE.woff

KFOlCnqEu92Fr1MmWUlvAB0_IsE.woff

502 ms

KFOlCnqEu92Fr1MmYUtvAB0_IsE.woff

KFOlCnqEu92Fr1MmYUtvAB0_IsE.woff

501 ms

recaptcha__en.js

recaptcha__en.js

481 ms

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B1i0HTuB9ptHSpA.woff

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B1i0HTuB9ptHSpA.woff

371 ms

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B7y0HTuB9ptHSpA.woff

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B7y0HTuB9ptHSpA.woff

372 ms

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BAyoHTuB9ptHSpA.woff

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BAyoHTuB9ptHSpA.woff

371 ms

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSoHTuB9ptHSpA.woff

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSoHTuB9ptHSpA.woff

370 ms

fa-solid-900.woff

fa-solid-900.woff

368 ms

fa-regular-400.woff

fa-regular-400.woff

368 ms

fa-brands-400.woff

fa-brands-400.woff

369 ms

ajax-loader.gif

ajax-loader.gif

141 ms

slick.woff

slick.woff

142 ms

17199108742045559095.avif

17199108742045559095.avif

24 ms

17245672881229133865.avif

17245672881229133865.avif

24 ms

Accessibility Review

royalpepperbanquets.com accessibility score

76

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

royalpepperbanquets.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

royalpepperbanquets.com SEO score

79

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

High

robots.txt is not valid

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

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 Royalpepperbanquets.com 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 Royalpepperbanquets.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

royalpepperbanquets.com

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