Tools & Wizards About Us
waterkingdom.in screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

waterkingdom.in

Water Kingdom, Mumbai | Best Water Park in Mumbai

Page Load Speed

7.6 sec in total

First Response

558 ms

Resources Loaded

5.4 sec

Page Rendered

1.6 sec

waterkingdom.in screenshot

About Website

Welcome to waterkingdom.in homepage info - get ready to check Water Kingdom best content for India right away, or after learning these important things about waterkingdom.in

imagemarker.com

Visit waterkingdom.in

Key Findings

We analyzed Waterkingdom.in page load time and found that the first response time was 558 ms and then it took 7 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

waterkingdom.in performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value15.1 s

1/100

10%

TBT (Total Blocking Time)

Value8,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value33.0 s

0/100

10%

Network Requests Diagram

waterkingdom.in

558 ms

www.waterkingdom.in

1318 ms

css

105 ms

css

136 ms

all.min.css

115 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Waterkingdom.in, 27% (31 requests) were made to Res.cloudinary.com and 12% (14 requests) were made to Cdn.simplotel.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Bookings.simplotel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 276.8 kB (5%)

Content Size

5.7 MB

After Optimization

5.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waterkingdom.in main page is 5.7 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. Only a small number of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 92.5 kB

  • Original 115.3 kB
  • After minification 115.3 kB
  • After compression 22.8 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 92.5 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 154.9 kB

  • Original 5.2 MB
  • After minification 5.0 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. Water Kingdom images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 26.9 kB

  • Original 349.8 kB
  • After minification 340.0 kB
  • After compression 322.9 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

-2%

Potential reduce by 2.5 kB

  • Original 114.3 kB
  • After minification 114.3 kB
  • After compression 111.9 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. Waterkingdom.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (38%)

Requests Now

91

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Water Kingdom. 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 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

waterkingdom.in

waterkingdom.in

558 ms

www.waterkingdom.in

www.waterkingdom.in

1318 ms

css

css

105 ms

css

css

136 ms

all.min.css

all.min.css

115 ms

v4-shims.min.css

v4-shims.min.css

125 ms

animate.css

animate.css

122 ms

simp.min.993ff750e0206190e2a34858782cfe47.css

simp.min.993ff750e0206190e2a34858782cfe47.css

136 ms

custom-plugins.1ad37b31ed9628fd09dc557ccf66e653.css

custom-plugins.1ad37b31ed9628fd09dc557ccf66e653.css

129 ms

Water_Kingdomtrans_u6eciw

Water_Kingdomtrans_u6eciw

153 ms

Web-Home_(6)

Web-Home_(6)

173 ms

Zd3x4PylyNA

Zd3x4PylyNA

216 ms

ct5D4Nk1oU4

ct5D4Nk1oU4

658 ms

FGTABm9GTVo

FGTABm9GTVo

728 ms

qiOB7dRSc64

qiOB7dRSc64

803 ms

a.js

a.js

144 ms

image-map-pro.min.css

image-map-pro.min.css

289 ms

squares.min.css

squares.min.css

289 ms

jquery.min.js

jquery.min.js

320 ms

image-map-pro.min.js

image-map-pro.min.js

319 ms

xdomain_cookie.min.js

xdomain_cookie.min.js

1803 ms

jssor.slider.min.js

jssor.slider.min.js

141 ms

1-simp-lib.min.ccd36ab4483dd0ad6f407b92977e62c9.js

1-simp-lib.min.ccd36ab4483dd0ad6f407b92977e62c9.js

121 ms

2-simp-lib.min.67ef317b27fb7f855bdae3cedc9075b4.js

2-simp-lib.min.67ef317b27fb7f855bdae3cedc9075b4.js

117 ms

3-simp-lib.min.e2ed483c22f4c3cce694b4a13b97c7b8.js

3-simp-lib.min.e2ed483c22f4c3cce694b4a13b97c7b8.js

118 ms

4-simp-lib.min.f6c16e3acd3502675b92b52876190ec4.js

4-simp-lib.min.f6c16e3acd3502675b92b52876190ec4.js

137 ms

5-simp-lib.min.9bde239aed1d6157fd5fda5927ab23a0.js

5-simp-lib.min.9bde239aed1d6157fd5fda5927ab23a0.js

136 ms

bookingengine.min.8e04c19f47e64cba4edc0fff4269ca56.js

bookingengine.min.8e04c19f47e64cba4edc0fff4269ca56.js

136 ms

jquery.viewportchecker.min.js

jquery.viewportchecker.min.js

149 ms

sm-bookingengine.js

sm-bookingengine.js

564 ms

mhd5nuo.css

mhd5nuo.css

182 ms

slu6joa.css

slu6joa.css

805 ms

guf6ykh.css

guf6ykh.css

282 ms

js

js

167 ms

A-PARAGON-OF-SPLENDOUR_jlkp6a

A-PARAGON-OF-SPLENDOUR_jlkp6a

564 ms

Web-home_4_a7fzni

Web-home_4_a7fzni

562 ms

amusement-park_1_ofa0ei

amusement-park_1_ofa0ei

559 ms

amusement-park_xhk4qz

amusement-park_xhk4qz

560 ms

amusement-park_5_h83qlt

amusement-park_5_h83qlt

796 ms

amusement-park_6_h5pi4i

amusement-park_6_h5pi4i

646 ms

1.2-Ratio-3_1_urra7n

1.2-Ratio-3_1_urra7n

798 ms

1.2-Ratio-4_1_qgwbya

1.2-Ratio-4_1_qgwbya

797 ms

1.2-Ratio-2_1_nexyn2

1.2-Ratio-2_1_nexyn2

799 ms

jungleBeach03_nxnnxv

jungleBeach03_nxnnxv

795 ms

WETLANTIC_1_iwufxv

WETLANTIC_1_iwufxv

800 ms

WETLANTIC_4_upnffg

WETLANTIC_4_upnffg

797 ms

JS1_8683_z3e4li

JS1_8683_z3e4li

802 ms

WETLANTI_ggr8l2

WETLANTI_ggr8l2

1005 ms

JAS_1983_exnhty

JAS_1983_exnhty

799 ms

Adventure_Amazonia_3_kbg1ee

Adventure_Amazonia_3_kbg1ee

1004 ms

JS1_8661_qummmh

JS1_8661_qummmh

999 ms

pexels-juan-salamanca-61129_wruylb

pexels-juan-salamanca-61129_wruylb

1005 ms

jungleBeachBoat_ccl4dr

jungleBeachBoat_ccl4dr

1004 ms

KIDDIES__ejluuu

KIDDIES__ejluuu

1003 ms

WETLANTIC_4_upnffg

WETLANTIC_4_upnffg

1415 ms

Bird_Park_g2k1vo_stu71w_nekztt

Bird_Park_g2k1vo_stu71w_nekztt

1295 ms

google_g_icon_download_tvcuh3

google_g_icon_download_tvcuh3

1145 ms

facebook_taqgrg

facebook_taqgrg

1145 ms

www-player.css

www-player.css

13 ms

www-embed-player.js

www-embed-player.js

39 ms

base.js

base.js

113 ms

simp.min.993ff750e0206190e2a34858782cfe47.css

simp.min.993ff750e0206190e2a34858782cfe47.css

492 ms

close.png

close.png

1173 ms

loading.gif

loading.gif

1171 ms

prev.png

prev.png

1171 ms

next.png

next.png

1109 ms

bg_grad_x29xge

bg_grad_x29xge

841 ms

ad_status.js

ad_status.js

615 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

614 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

989 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

1044 ms

fa-light-300.woff

fa-light-300.woff

496 ms

fa-regular-400.woff

fa-regular-400.woff

354 ms

fa-solid-900.woff

fa-solid-900.woff

350 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

1069 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

1044 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

1069 ms

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

581 ms

embed.js

embed.js

160 ms

Water_kingdomfooter_l7o688

Water_kingdomfooter_l7o688

399 ms

id

id

331 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

444 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

441 ms

Create

Create

429 ms

Create

Create

426 ms

Create

Create

431 ms

Create

Create

430 ms

xdomain_cookie.html

xdomain_cookie.html

521 ms

ui-bg_glass_55_FFFFFF_1x400.png

ui-bg_glass_55_FFFFFF_1x400.png

1094 ms

fbevents.js

fbevents.js

290 ms

google_play_erdugv

google_play_erdugv

291 ms

p.css

p.css

437 ms

p.css

p.css

438 ms

p.css

p.css

439 ms

image00001_wu97hl

image00001_wu97hl

195 ms

Regular-Ticket-v3_oxsk9q

Regular-Ticket-v3_oxsk9q

305 ms

GenerateIT

GenerateIT

350 ms

GenerateIT

GenerateIT

348 ms

GenerateIT

GenerateIT

218 ms

GenerateIT

GenerateIT

82 ms

fa-brands-400.woff

fa-brands-400.woff

44 ms

d

d

110 ms

d

d

110 ms

d

d

177 ms

d

d

204 ms

d

d

128 ms

analytics.js

analytics.js

102 ms

collect

collect

36 ms

collect

collect

51 ms

collect

collect

78 ms

js

js

39 ms

js

js

64 ms

ga-audiences

ga-audiences

111 ms

tp.js

tp.js

249 ms

Accessibility Review

waterkingdom.in accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

waterkingdom.in 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

waterkingdom.in SEO score

85

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waterkingdom.in 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 Waterkingdom.in 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

waterkingdom.in

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