5.1 sec in total
496 ms
3.5 sec
1.1 sec
Click here to check amazing Hotel Lineage content. Otherwise, check out these important facts you probably never knew about hotellineage.com
Welcome to lineage hotel lucknow,We introduce ourselves as Hotel Lineage - a business class Hotel - centrally located just opposite the renowned Sahara Hospital at Gomti Nagar , Lucknow ( U.P.)
Visit hotellineage.comWe analyzed Hotellineage.com page load time and found that the first response time was 496 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
hotellineage.com performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value35.2 s
0/100
25%
Value20.5 s
0/100
10%
Value450 ms
62/100
30%
Value0
100/100
15%
Value28.7 s
0/100
10%
496 ms
160 ms
233 ms
328 ms
218 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 95% of them (74 requests) were addressed to the original Hotellineage.com, 5% (4 requests) were made to Fast.fonts.com. The less responsive or slowest element that took the longest time to load (977 ms) belongs to the original domain Hotellineage.com.
Page size can be reduced by 733.0 kB (28%)
2.6 MB
1.9 MB
In fact, the total size of Hotellineage.com main page is 2.6 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 28.5 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 4.3 kB, which is 11% 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 28.5 kB or 75% of the original size.
Potential reduce by 24.1 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. Hotel Lineage images are well optimized though.
Potential reduce by 574.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 574.9 kB or 73% of the original size.
Potential reduce by 105.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. Hotellineage.com needs all CSS files to be minified and compressed as it can save up to 105.5 kB or 83% of the original size.
Number of requests can be reduced by 28 (45%)
62
34
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hotel Lineage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
hotellineage.com
496 ms
index.php
160 ms
all.js
233 ms
ga.js
328 ms
dec9e8cd-9fa4-49a5-87ff-42d83acb4e2e.js
218 ms
supersized.css
217 ms
jquery.fancybox.css
212 ms
photoswipe.css
227 ms
style.css
326 ms
jqueryDatepicker.css
370 ms
klass.min.js
348 ms
jquery.min.js
474 ms
jqueryDatepicker.js
401 ms
jquery.fancybox.js
427 ms
code.photoswipe.jquery-3.0.5.min.js
435 ms
checkform.js
425 ms
supersized.3.2.7.min.js
437 ms
shutter.js
460 ms
scripts.js
546 ms
1.css
544 ms
translateelement.css
546 ms
reset.css
216 ms
imageSprite.png
682 ms
logo1.png
969 ms
93_11_lobby-chair-hotel-hamburg-alster.jpg
121 ms
224_11_rezeption-british-hotel-hamburg.jpg
178 ms
2401_11_hotel-hamburg-alster-city-design.jpg
173 ms
2402_11_hotel-hamburg-alster-city-libary.jpg
140 ms
2403_11_hotel-hamburg-alster-city-design-keys.jpg
304 ms
93_2_lobby-chair-hotel-hamburg-alster.jpg
296 ms
224_2_rezeption-british-hotel-hamburg.jpg
297 ms
2401_2_hotel-hamburg-alster-city-design.jpg
298 ms
2402_2_hotel-hamburg-alster-city-libary.jpg
452 ms
2403_2_hotel-hamburg-alster-city-design-keys.jpg
455 ms
sld2.png
522 ms
sld1.png
636 ms
logo.png
516 ms
index.php
395 ms
bgBlack40.png
423 ms
bgBlack20.png
472 ms
bgBlack75.png
498 ms
progress.gif
208 ms
closeCursor.cur
247 ms
THE%20URBAN%20TERRACE%20(2).jpg
483 ms
HOTEL%20LOBBY%201.jpg
379 ms
CLUB%20ROOM%201.jpg
406 ms
DELUXE%20ROOM%203.jpg
583 ms
hotel.jpg
586 ms
ga.js.pagespeed.jm.tARqGQ7NHZ.js
504 ms
dec9e8cd-9fa4-49a5-87ff-42d83acb4e2e.js+klass.min.js.pagespeed.jc.BdDsZej1-3.js
504 ms
A.supersized.css+jquery.fancybox.css+photoswipe.css,Mcc.TcpXt9Uu2D.css.pagespeed.cf.lokIvv2QHv.css
548 ms
A.style.css+jqueryDatepicker.css,Mcc.krUxpK3idQ.css.pagespeed.cf.DP7a5rMleM.css
567 ms
jquery.min.js.pagespeed.jm.a-tJGu7l62.js
615 ms
jqueryDatepicker.js.pagespeed.jm.FDnlwRi-Cz.js
612 ms
jquery.fancybox.js.pagespeed.jm.1ox8MZGJUo.js
623 ms
code.photoswipe.jquery-3.0.5.min.js+checkform.js.pagespeed.jc.tEhTcWqlHe.js
649 ms
supersized.3.2.7.min.js+shutter.js+scripts.js.pagespeed.jc.dQaijhsDjr.js
683 ms
1.css
677 ms
translateelement.css
758 ms
1c7e8feb-d184-494e-8619-777ea84813c4.woff
113 ms
1d969a3e-30d0-4540-946b-30330632931a.woff
125 ms
xlogo1.png.pagespeed.ic.TAb5zGTHow.png
977 ms
x93_11_lobby-chair-hotel-hamburg-alster.jpg.pagespeed.ic.NVlfSQOVfj.jpg
171 ms
x224_11_rezeption-british-hotel-hamburg.jpg.pagespeed.ic.98BjMzIHUH.jpg
166 ms
x2401_11_hotel-hamburg-alster-city-design.jpg.pagespeed.ic.i3KsuFexJW.jpg
173 ms
x2402_11_hotel-hamburg-alster-city-libary.jpg.pagespeed.ic.dq_kd2T782.jpg
142 ms
x2403_11_hotel-hamburg-alster-city-design-keys.jpg.pagespeed.ic.l2M4aEkHgv.jpg
228 ms
224_2_rezeption-british-hotel-hamburg.jpg
271 ms
xsld2.png.pagespeed.ic.9HTHHu8BgY.png
431 ms
xsld1.png.pagespeed.ic.TnrcIOIulq.png
304 ms
174x108xlogo.png.pagespeed.ic.0Z3U3ctvLy.png
336 ms
ximageSprite.png.pagespeed.ic.G9hY4soRJw.png
805 ms
xbgBlack40.png.pagespeed.ic.igGmB6tLJS.png
333 ms
xbgBlack20.png.pagespeed.ic.igGmB6tLJS.png
368 ms
cLounge.png
382 ms
xbgBlack75.png.pagespeed.ic.miRcCPr3JZ.png
438 ms
1c7e8feb-d184-494e-8619-777ea84813c4.woff
12 ms
1d969a3e-30d0-4540-946b-30330632931a.woff
13 ms
hotellineage.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hotellineage.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
hotellineage.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotellineage.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Hotellineage.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.
hotellineage.com
Open Graph description is not detected on the main page of Hotel Lineage. 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: