Tools & Wizards About Us
thelotus.in screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

thelotus.in

The Lotus Apartment Hotel – Budget Hotel in T.Nagar Chennai

Page Load Speed

1.7 sec in total

First Response

206 ms

Resources Loaded

990 ms

Page Rendered

524 ms

thelotus.in screenshot

About Website

Visit thelotus.in now to see the best up-to-date The Lotus content for India and also check out these interesting facts you probably never knew about thelotus.in

Visit thelotus.in

Key Findings

We analyzed Thelotus.in page load time and found that the first response time was 206 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

thelotus.in performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

thelotus.in

206 ms

main.css

12 ms

style.min.css

22 ms

nectar-slider.css

40 ms

font-awesome-legacy.min.css

19 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 84% of them (64 requests) were addressed to the original Thelotus.in, 13% (10 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (206 ms) belongs to the original domain Thelotus.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 292.5 kB (7%)

Content Size

4.3 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thelotus.in main page is 4.3 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 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 94.3 kB

  • Original 117.2 kB
  • After minification 113.5 kB
  • After compression 22.9 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 94.3 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 115.2 kB

  • Original 3.7 MB
  • After minification 3.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. The Lotus images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 63.5 kB

  • Original 291.0 kB
  • After minification 291.0 kB
  • After compression 227.5 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 63.5 kB or 22% of the original size.

CSS Optimization

-11%

Potential reduce by 19.4 kB

  • Original 177.0 kB
  • After minification 177.0 kB
  • After compression 157.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. Thelotus.in needs all CSS files to be minified and compressed as it can save up to 19.4 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (77%)

Requests Now

62

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thelotus.in

thelotus.in

206 ms

main.css

main.css

12 ms

style.min.css

style.min.css

22 ms

nectar-slider.css

nectar-slider.css

40 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

19 ms

grid-system.css

grid-system.css

16 ms

style.css

style.css

25 ms

header-secondary-nav.css

header-secondary-nav.css

21 ms

element-testimonial.css

element-testimonial.css

38 ms

element-fancy-box.css

element-fancy-box.css

41 ms

element-icon-list.css

element-icon-list.css

37 ms

element-fancy-unordered-list.css

element-fancy-unordered-list.css

37 ms

element-milestone.css

element-milestone.css

55 ms

asset-reveal-animation.css

asset-reveal-animation.css

44 ms

css

css

69 ms

masonry-classic-enhanced.css

masonry-classic-enhanced.css

45 ms

standard-minimal.css

standard-minimal.css

54 ms

responsive.css

responsive.css

42 ms

flickity.css

flickity.css

48 ms

ascend.css

ascend.css

45 ms

menu-dynamic.css

menu-dynamic.css

53 ms

default.css

default.css

53 ms

js_composer.min.css

js_composer.min.css

51 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

56 ms

css

css

73 ms

jquery.min.js

jquery.min.js

54 ms

jquery-migrate.min.js

jquery-migrate.min.js

54 ms

animate.min.css

animate.min.css

60 ms

iconsmind-core.css

iconsmind-core.css

54 ms

magnific.css

magnific.css

58 ms

core.css

core.css

59 ms

app.js

app.js

61 ms

anime.js

anime.js

60 ms

nectar-slider.js

nectar-slider.js

61 ms

jquery.easing.js

jquery.easing.js

62 ms

jquery.mousewheel.js

jquery.mousewheel.js

62 ms

priority.js

priority.js

62 ms

transit.js

transit.js

65 ms

waypoints.js

waypoints.js

64 ms

imagesLoaded.min.js

imagesLoaded.min.js

58 ms

hoverintent.js

hoverintent.js

50 ms

magnific.js

magnific.js

50 ms

nectar-testimonial-slider.js

nectar-testimonial-slider.js

49 ms

flickity.min.js

flickity.min.js

50 ms

superfish.js

superfish.js

36 ms

init.js

init.js

36 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

32 ms

isotope.min.js

isotope.min.js

34 ms

nectar-blog.js

nectar-blog.js

30 ms

touchswipe.min.js

touchswipe.min.js

28 ms

js_composer_front.min.js

js_composer_front.min.js

29 ms

Lotus_Logo.jpg

Lotus_Logo.jpg

196 ms

slider-1-1.jpg

slider-1-1.jpg

97 ms

Banquet-hall.jpg

Banquet-hall.jpg

24 ms

experience.jpg

experience.jpg

97 ms

lotus-about-V2.jpg

lotus-about-V2.jpg

96 ms

Rock-climbing.jpg

Rock-climbing.jpg

9 ms

Travel-Charger.jpg

Travel-Charger.jpg

16 ms

The-squad-that-travels-together-stays-together.jpg

The-squad-that-travels-together-stays-together.jpg

15 ms

call-t-action.jpg

call-t-action.jpg

97 ms

lotus-logo.png

lotus-logo.png

22 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

21 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

23 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

93 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

94 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

98 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

98 ms

icomoon.woff

icomoon.woff

20 ms

iconsmind.ttf

iconsmind.ttf

98 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

97 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

98 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

97 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

97 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

94 ms

thelotus.in

thelotus.in

168 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

30 ms

Accessibility Review

thelotus.in accessibility score

59

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

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

Links do not have a discernible name

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

thelotus.in best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

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

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

thelotus.in

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