Tools & Wizards About Us
royal19.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

royal19.com

Full body massage, body massage, thai massage, aromatherapy massage, deep tissue massage, facial, body wrap, body polish at Royal 19 Thai Spa Pune, Th...

Page Load Speed

7.5 sec in total

First Response

1.1 sec

Resources Loaded

5 sec

Page Rendered

1.4 sec

royal19.com screenshot

About Website

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

Royal 19 Thai Spa Pune, Thai Spa in Pune, full body massage, body massage, thai massage, aromatherapy massage, deep tissue massage, facial

Visit royal19.com

Key Findings

We analyzed Royal19.com page load time and found that the first response time was 1.1 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

royal19.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value1.179

1/100

15%

TTI (Time to Interactive)

Value8.5 s

37/100

10%

Network Requests Diagram

royal19.com

1057 ms

style.css

998 ms

responsive.css

513 ms

logo.png

714 ms

slider01.jpg

1218 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 89% of them (67 requests) were addressed to the original Royal19.com, 9% (7 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Royal19.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 805.2 kB (46%)

Content Size

1.8 MB

After Optimization

960.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-91%

Potential reduce by 47.1 kB

  • Original 51.6 kB
  • After minification 26.6 kB
  • After compression 4.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 25.0 kB, which is 48% 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 47.1 kB or 91% of the original size.

Image Optimization

-28%

Potential reduce by 319.0 kB

  • Original 1.2 MB
  • After minification 836.2 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. Obviously, Royal 19 needs image optimization as it can save up to 319.0 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 154.2 kB

  • Original 222.9 kB
  • After minification 210.5 kB
  • After compression 68.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 154.2 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 285.0 kB

  • Original 336.5 kB
  • After minification 291.0 kB
  • After compression 51.5 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. Royal19.com needs all CSS files to be minified and compressed as it can save up to 285.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (37%)

Requests Now

63

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royal19.com

royal19.com

1057 ms

style.css

style.css

998 ms

responsive.css

responsive.css

513 ms

logo.png

logo.png

714 ms

slider01.jpg

slider01.jpg

1218 ms

slider02.jpg

slider02.jpg

1544 ms

slider03.jpg

slider03.jpg

1046 ms

icon01.png

icon01.png

782 ms

icon02.png

icon02.png

963 ms

icon03.png

icon03.png

1046 ms

wat.gif

wat.gif

972 ms

1.png

1.png

1026 ms

2.png

2.png

1099 ms

3.png

3.png

1338 ms

4.png

4.png

1483 ms

portfolio01.png

portfolio01.png

1226 ms

portfolio02.png

portfolio02.png

1287 ms

portfolio05.png

portfolio05.png

1366 ms

222.png

222.png

1527 ms

portfolio07.png

portfolio07.png

1564 ms

portfolio08.png

portfolio08.png

1603 ms

portfolio03.png

portfolio03.png

1636 ms

feature-icon02.png

feature-icon02.png

1702 ms

Aroma%20Therapy.jpg

Aroma%20Therapy.jpg

1722 ms

1.jpg

1.jpg

1783 ms

2.jpg

2.jpg

1832 ms

3.jpg

3.jpg

1839 ms

section-icon.png

section-icon.png

1880 ms

fb1.jpg

fb1.jpg

1954 ms

fb2.jpg

fb2.jpg

1975 ms

fb3.jpg

fb3.jpg

2020 ms

fb4.jpg

fb4.jpg

2149 ms

fb5.jpg

fb5.jpg

2159 ms

fb6.jpg

fb6.jpg

2153 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

2074 ms

popper.min.js

popper.min.js

2039 ms

bootstrap.min.js

bootstrap.min.js

2082 ms

jquery.sticky.js

jquery.sticky.js

2001 ms

owl.carousel.min.js

owl.carousel.min.js

1895 ms

jquery.shuffle.min.js

jquery.shuffle.min.js

1797 ms

css

css

80 ms

fontawesome-all.min.css

fontawesome-all.min.css

1811 ms

elegant-icons.min.css

elegant-icons.min.css

1877 ms

bootstrap.min.css

bootstrap.min.css

1845 ms

meanmenu.min.css

meanmenu.min.css

1727 ms

owl.carousel.min.css

owl.carousel.min.css

1762 ms

owl.theme.default.min.css

owl.theme.default.min.css

1739 ms

animate.css

animate.css

1734 ms

magnific-popup.css

magnific-popup.css

1677 ms

typograhpy.css

typograhpy.css

1711 ms

default.css

default.css

1640 ms

widget.css

widget.css

1687 ms

jquery.counterup.min.js

jquery.counterup.min.js

1983 ms

wow.min.js

wow.min.js

1891 ms

jquery.meanmenu.min.js

jquery.meanmenu.min.js

1871 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1825 ms

custom.js

custom.js

1797 ms

mastercard.png

mastercard.png

1750 ms

shopify.png

shopify.png

1723 ms

feature-bg.jpg

feature-bg.jpg

783 ms

testimonial-bg.jpg

testimonial-bg.jpg

811 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf

550 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf

554 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf

585 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf

554 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0Uw.ttf

553 ms

fa-solid-900.woff

fa-solid-900.woff

549 ms

fa-regular-400.woff

fa-regular-400.woff

548 ms

fa-brands-400.woff

fa-brands-400.woff

547 ms

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B1i03Sup5.ttf

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B1i03Sup5.ttf

578 ms

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSo3Sup5.ttf

If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSo3Sup5.ttf

577 ms

ElegantIcons746c.woff

ElegantIcons746c.woff

541 ms

testimonial01.png

testimonial01.png

293 ms

testimonial02.png

testimonial02.png

289 ms

testimonial03.png

testimonial03.png

302 ms

Accessibility Review

royal19.com accessibility score

90

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

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>).

Best Practices

royal19.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

High

Page has valid source maps

SEO Factors

royal19.com SEO score

98

Search Engine Optimization Advices

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 Royal19.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 Royal19.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

royal19.com

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