10.8 sec in total
1.3 sec
9.1 sec
401 ms
Welcome to grange-hotel.co.uk homepage info - get ready to check Grange Hotel best content right away, or after learning these important things about grange-hotel.co.uk
The Grange Hotel in Grange-over-Sands, the English Lake District. With bay views and near to Lake Windermere and Lake District National Park.
Visit grange-hotel.co.ukWe analyzed Grange-hotel.co.uk page load time and found that the first response time was 1.3 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
grange-hotel.co.uk performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value29.7 s
0/100
25%
Value18.3 s
0/100
10%
Value11,500 ms
0/100
30%
Value0.038
100/100
15%
Value33.5 s
0/100
10%
1334 ms
25 ms
59 ms
49 ms
35 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 66% of them (89 requests) were addressed to the original Grange-hotel.co.uk, 13% (18 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Grange-hotel.co.uk.
Page size can be reduced by 216.7 kB (24%)
901.1 kB
684.4 kB
In fact, the total size of Grange-hotel.co.uk main page is 901.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% 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 575.8 kB which makes up the majority of the site volume.
Potential reduce by 177.7 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 177.7 kB or 83% of the original size.
Potential reduce by 12.6 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. Grange Hotel images are well optimized though.
Potential reduce by 26.4 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 26.4 kB or 24% of the original size.
Number of requests can be reduced by 78 (72%)
108
30
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grange Hotel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
grange-hotel.co.uk
1334 ms
main.min.css
25 ms
css
59 ms
cookie-law-info-public.css
49 ms
cookie-law-info-gdpr.css
35 ms
elementor-icons.min.css
38 ms
frontend.min.css
41 ms
swiper.min.css
51 ms
post-9.css
49 ms
frontend.min.css
57 ms
slick.css
49 ms
slick-theme.css
70 ms
style.css
72 ms
all.min.css
72 ms
v4-shims.min.css
69 ms
she-header-style.css
71 ms
global.css
79 ms
post-17.css
1041 ms
post-266.css
77 ms
post-283.css
79 ms
post-12050.css
78 ms
general.min.css
84 ms
fontawesome.min.css
89 ms
solid.min.css
93 ms
brands.min.css
88 ms
jquery.min.js
87 ms
jquery-migrate.min.js
93 ms
cookie-law-info-public.js
96 ms
v4-shims.min.js
96 ms
she-header.js
102 ms
asktag.js
85 ms
infochat.js
85 ms
js
78 ms
cookie-law-info-table.css
94 ms
post-14505.css
101 ms
animations.min.css
101 ms
email-decode.min.js
95 ms
frontend.min.js
121 ms
slick.js
105 ms
main.js
107 ms
general.min.js
108 ms
jquery.smartmenus.min.js
89 ms
imagesloaded.min.js
90 ms
webpack-pro.runtime.min.js
90 ms
webpack.runtime.min.js
81 ms
frontend-modules.min.js
87 ms
wp-polyfill-inert.min.js
87 ms
regenerator-runtime.min.js
95 ms
wp-polyfill.min.js
73 ms
hooks.min.js
73 ms
i18n.min.js
73 ms
frontend.min.js
73 ms
waypoints.min.js
75 ms
core.min.js
79 ms
swiper.min.js
75 ms
share-link.min.js
74 ms
dialog.min.js
80 ms
frontend.min.js
80 ms
preloaded-elements-handlers.min.js
82 ms
preloaded-modules.min.js
75 ms
jquery.sticky.min.js
72 ms
underscore.min.js
78 ms
wp-util.min.js
76 ms
frontend.min.js
74 ms
lazyload.min.js
75 ms
distributor.js
37 ms
asktag.postload.js
60 ms
gtm.js
113 ms
fbevents.js
162 ms
The-Grange-Stay.jpg
136 ms
The-Grange-Dining.jpg
1606 ms
The-Grange-Events.jpg
1592 ms
The-Grange-Special-Offers.jpg
1889 ms
js
177 ms
analytics.js
176 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf
176 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf
176 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf
284 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf
292 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf
352 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf
337 ms
proximanovalight.woff
1577 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXtHA_A.ttf
351 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_pqTXtHA_A.ttf
329 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_naUXtHA_A.ttf
352 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UXtHA_A.ttf
352 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_iiUXtHA_A.ttf
369 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUXtHA_A.ttf
369 ms
eicons.woff
1940 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
369 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
368 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
368 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
368 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
387 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
386 ms
fa-brands-400.woff
1648 ms
fa-solid-900.woff
3445 ms
fa-regular-400.woff
2785 ms
admin-ajax.php
3141 ms
250 ms
bootstrap.js
361 ms
js
187 ms
ugx.js
481 ms
gxm9q2pax4
273 ms
loader.js
320 ms
Grange-Hotel-Logo-White.png
1494 ms
Divider-Icon.svg
1500 ms
THE-GRANGE-323-1024x684.jpg
3151 ms
DINNER-AT-THE-GRANGE-HOTEL-02-1024x684.jpg
3209 ms
The-Grange-Events-1024x576.jpg
3396 ms
Logo-for-Footer.svg
3584 ms
PH.svg
3015 ms
safe-travels-grange-hotel.png
3025 ms
tchotel_2022_LL.png
3034 ms
brides-grange-hotel.png
3043 ms
loved-by-guest-grange-hotel-150x150.png
3058 ms
travelmyth-grange-hotel-150x150.png
3067 ms
TC-Sticker-2023_White.gif
3079 ms
logo-cookieyes.svg
3089 ms
Group-435@2x.png
4405 ms
Headland_White-SVG_1.svg
4112 ms
Palace-Hotel-Logo.svg
4195 ms
Queens-White.png
4232 ms
160 ms
collect
82 ms
collect
61 ms
54 ms
clarity.js
30 ms
32 ms
25 ms
distributor.js
17 ms
bootstrap.js
63 ms
ug_core.js
185 ms
c.gif
32 ms
grange-hotel.co.uk 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
grange-hotel.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
grange-hotel.co.uk SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grange-hotel.co.uk 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 Grange-hotel.co.uk 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.
grange-hotel.co.uk
Open Graph data is detected on the main page of Grange Hotel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: