Tools & Wizards About Us
gatewaygrandeur.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

gatewaygrandeur.com

Hotel Gateway Grandeur - Hotels in Guwahati, Hotel in Guwahati, 4 star hotel in Guwahati, Luxury Hotel in Guwahati, Budget hotel in Guwahati, Guwahati...

Page Load Speed

1.6 sec in total

First Response

91 ms

Resources Loaded

670 ms

Page Rendered

789 ms

gatewaygrandeur.com screenshot

About Website

Welcome to gatewaygrandeur.com homepage info - get ready to check Gateway Grandeur best content right away, or after learning these important things about gatewaygrandeur.com

Hotels in Guwahati, Hotel in Guwahati, 4 star hotel in Guwahati, Luxury Hotel in Guwahati, Budget hotel in Guwahati, Guwahati City, Guwahati Hotel, Hotel Gateway Grandeur, Hotels in Northeast, Economy...

Visit gatewaygrandeur.com

Key Findings

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

gatewaygrandeur.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value1.034

2/100

15%

TTI (Time to Interactive)

Value8.4 s

38/100

10%

Network Requests Diagram

gatewaygrandeur.com

91 ms

theme.fonts.css

30 ms

bootstrap.min.css

63 ms

jquery-ui.min.css

43 ms

plugin.style.css

40 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 93% of them (41 requests) were addressed to the original Gatewaygrandeur.com, 5% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (479 ms) belongs to the original domain Gatewaygrandeur.com.

Page Optimization Overview & Recommendations

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

Content Size

2.4 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gatewaygrandeur.com main page is 2.4 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. 80% 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 36.0 kB

  • Original 41.0 kB
  • After minification 27.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 13.1 kB, which is 32% 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 36.0 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 23.3 kB

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

JavaScript Optimization

-27%

Potential reduce by 57.2 kB

  • Original 210.0 kB
  • After minification 210.0 kB
  • After compression 152.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 57.2 kB or 27% of the original size.

CSS Optimization

-33%

Potential reduce by 33.8 kB

  • Original 103.4 kB
  • After minification 103.4 kB
  • After compression 69.6 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. Gatewaygrandeur.com needs all CSS files to be minified and compressed as it can save up to 33.8 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (39%)

Requests Now

38

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gatewaygrandeur.com

gatewaygrandeur.com

91 ms

theme.fonts.css

theme.fonts.css

30 ms

bootstrap.min.css

bootstrap.min.css

63 ms

jquery-ui.min.css

jquery-ui.min.css

43 ms

plugin.style.css

plugin.style.css

40 ms

global.css

global.css

42 ms

style.css

style.css

59 ms

color-1.css

color-1.css

53 ms

responsive.css

responsive.css

75 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

120 ms

popper.min.js

popper.min.js

72 ms

bootstrap.min.js

bootstrap.min.js

77 ms

owl.carousel.min.js

owl.carousel.min.js

80 ms

slick.js

slick.js

152 ms

jquery-ui.min.js

jquery-ui.min.js

170 ms

plugin.js

plugin.js

161 ms

main.js

main.js

162 ms

logo.png

logo.png

163 ms

welcome-img1.jpg

welcome-img1.jpg

163 ms

welcome-img2.jpg

welcome-img2.jpg

164 ms

welcome-img3.jpg

welcome-img3.jpg

165 ms

royal.jpg

royal.jpg

439 ms

kqg_room.jpg

kqg_room.jpg

439 ms

club_room.jpg

club_room.jpg

437 ms

bliss.jpg

bliss.jpg

438 ms

hill_view.jpg

hill_view.jpg

440 ms

executive.jpg

executive.jpg

440 ms

meeting_planers.jpg

meeting_planers.jpg

442 ms

foods.jpg

foods.jpg

440 ms

spa_saloon.jpg

spa_saloon.jpg

440 ms

gym.jpg

gym.jpg

441 ms

florentine.jpg

florentine.jpg

478 ms

camellia.jpg

camellia.jpg

477 ms

rainforest.jpg

rainforest.jpg

479 ms

css

css

46 ms

slider-img1.jpg

slider-img1.jpg

365 ms

slider-img2.jpg

slider-img2.jpg

367 ms

slider-img3.jpg

slider-img3.jpg

366 ms

font

font

322 ms

font

font

50 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

95 ms

ionicons.ttf

ionicons.ttf

95 ms

Flaticon.svg

Flaticon.svg

141 ms

Flaticon.woff

Flaticon.woff

121 ms

Accessibility Review

gatewaygrandeur.com accessibility score

64

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

gatewaygrandeur.com best practices score

83

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

Page has valid source maps

SEO Factors

gatewaygrandeur.com SEO score

72

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

gatewaygrandeur.com

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