6.3 sec in total
283 ms
4.3 sec
1.7 sec
Welcome to thehouseoftoby.london homepage info - get ready to check Thehouseoftoby best content right away, or after learning these important things about thehouseoftoby.london
Visit thehouseoftoby.londonWe analyzed Thehouseoftoby.london page load time and found that the first response time was 283 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
thehouseoftoby.london performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value13.4 s
0/100
25%
Value14.7 s
1/100
10%
Value1,840 ms
9/100
30%
Value0.076
95/100
15%
Value14.3 s
9/100
10%
283 ms
576 ms
227 ms
298 ms
313 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 82% of them (125 requests) were addressed to the original Thehouseoftoby.london, 8% (12 requests) were made to Fonts.gstatic.com and 4% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Thehouseoftoby.london.
Page size can be reduced by 390.2 kB (15%)
2.6 MB
2.2 MB
In fact, the total size of Thehouseoftoby.london 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 211.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 211.7 kB or 85% of the original size.
Potential reduce by 54.3 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. Thehouseoftoby images are well optimized though.
Potential reduce by 94.1 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 94.1 kB or 13% of the original size.
Potential reduce by 30.1 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. Thehouseoftoby.london needs all CSS files to be minified and compressed as it can save up to 30.1 kB or 28% of the original size.
Number of requests can be reduced by 101 (73%)
139
38
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thehouseoftoby. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
thehouseoftoby.london
283 ms
thehouseoftoby.london
576 ms
styles.css
227 ms
style.css
298 ms
style.css
313 ms
style.css
303 ms
css
40 ms
css
41 ms
css
42 ms
woocommerce-layout.css
333 ms
woocommerce.css
358 ms
style.css
471 ms
css
43 ms
frontend.min.css
418 ms
swiper.min.css
410 ms
e-swiper.min.css
425 ms
post-8.css
446 ms
fadeInUp.min.css
464 ms
rollIn.min.css
528 ms
widget-image.min.css
550 ms
widget-counter.min.css
527 ms
widget-heading.min.css
566 ms
widget-divider.min.css
571 ms
e-animation-shrink.min.css
584 ms
e-animation-float.min.css
639 ms
widget-icon-list.min.css
651 ms
fadeIn.min.css
657 ms
widget-spacer.min.css
676 ms
widget-google_maps.min.css
675 ms
post-17.css
704 ms
css
37 ms
jquery.min.js
859 ms
jquery-migrate.min.js
760 ms
jquery.blockUI.min.js
766 ms
add-to-cart.min.js
800 ms
js.cookie.min.js
788 ms
woocommerce.min.js
817 ms
js
87 ms
css
31 ms
wc-blocks.css
849 ms
post-46.css
849 ms
animations.min.css
851 ms
post-23.css
849 ms
widget-social-icons.min.css
853 ms
js
81 ms
apple-webkit.min.css
913 ms
rs6.css
923 ms
wp-polyfill-inert.min.js
723 ms
regenerator-runtime.min.js
845 ms
wp-polyfill.min.js
923 ms
hooks.min.js
842 ms
i18n.min.js
893 ms
main.js
846 ms
index.js
836 ms
index.js
830 ms
rbtools.min.js
1040 ms
rs6.min.js
1089 ms
sourcebuster.min.js
873 ms
order-attribution.min.js
821 ms
react.min.js
813 ms
deprecated.min.js
802 ms
dom.min.js
882 ms
react-dom.min.js
961 ms
escape-html.min.js
876 ms
element.min.js
819 ms
is-shallow-equal.min.js
899 ms
keycodes.min.js
915 ms
priority-queue.min.js
897 ms
compose.min.js
924 ms
private-apis.min.js
924 ms
redux-routine.min.js
894 ms
data.min.js
908 ms
lodash.min.js
923 ms
wc-blocks-registry.js
877 ms
url.min.js
886 ms
navigation-.white_.png
656 ms
navigation-.white_.png
746 ms
bag-icon.png
861 ms
api-fetch.min.js
830 ms
wc-settings.js
858 ms
data-controls.min.js
843 ms
html-entities.min.js
848 ms
notices.min.js
872 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
320 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
320 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
318 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
322 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
320 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
314 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf
318 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf
318 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf
317 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf
317 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf
316 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf
316 ms
wc-blocks-middleware.js
871 ms
wc-blocks-data.js
880 ms
dom-ready.min.js
844 ms
a11y.min.js
720 ms
embed
371 ms
primitives.min.js
721 ms
warning.min.js
721 ms
blocks-components.js
727 ms
blocks-checkout.js
823 ms
order-attribution-blocks.min.js
739 ms
comment-reply.min.js
771 ms
nicdark-navigation.js
752 ms
jquery-numerator.min.js
677 ms
navigation.js
733 ms
imagesloaded.min.js
762 ms
masonry.min.js
779 ms
rooms.js
677 ms
webpack.runtime.min.js
670 ms
frontend-modules.min.js
733 ms
core.min.js
692 ms
frontend.min.js
710 ms
js
43 ms
cropped-house-of-toby-hotel-logo-e1706405042847-2.png
683 ms
navigation-close.svg
686 ms
cropped-house-of-toby-hotel-logo-e1706405042847-2-qjkc9pqcdoe1pksybo8gzysa4rc13kd2esefv34uby.png
733 ms
dummy.png
723 ms
search.js
5 ms
geometry.js
8 ms
main.js
16 ms
HOUSE_OF_TOBY4748-scaled-3-720x720.jpg
822 ms
icon-7-2.png
700 ms
fa81fbb2-f5fa-4165-aafd-2f6d686c1bb8-2-1024x640.jpg
753 ms
icon-guests.png
686 ms
icon-size.png
719 ms
d933b0ab-2977-4777-a8a8-a90e1798aa5e-2-1024x640.jpg
820 ms
HOUSE_OF_TOBY4825-scaled-2-e1706318812182-2-1024x640.jpg
849 ms
No-Smoking-2.png
717 ms
icon-13-1-4.png
736 ms
icon-10-4.png
731 ms
HOUSE_OF_TOBY4831-1-720x720-1-3.jpg
781 ms
Airways-Hotel-111-720x720.jpg
862 ms
HOUSE_OF_TOBY4804-720x720-1-3.jpg
904 ms
pexels-%E1%BC%90%CE%BC%CE%BC%CE%B1%CE%BD%CF%85%CE%B5%CE%BB-%EF%A3%BF-12750234-3-qjkc9osisc20uchkjvj2ne22ycfdh5p4xr63cuo46g.jpg
850 ms
pexels-guillaume-meurice-2815036-3-qjkc9osisc20uchkjvj2ne22ycfdh5p4xr63cuo46g.jpg
892 ms
pexels-polina-zimmerman-3747505-2-3-qjkc9osisc20uchkjvj2ne22ycfdh5p4xr63cuo46g.jpg
856 ms
bg-dark-4.jpg
800 ms
bg1-4.jpg
913 ms
bg10-4.jpg
886 ms
parallax-3-2.jpg
947 ms
bg2-4.jpg
933 ms
bg5-4.jpg
962 ms
parallax-7-4.jpg
1371 ms
bg7-4.jpg
981 ms
bg9-4.jpg
978 ms
bg6-4.jpg
982 ms
HOUSE_OF_TOBY4631-scaled-3-720x720.jpg
1244 ms
bg8-4.jpg
1120 ms
woocommerce-smallscreen.css
107 ms
thehouseoftoby.london accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
thehouseoftoby.london best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
thehouseoftoby.london SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thehouseoftoby.london 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 Thehouseoftoby.london 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.
thehouseoftoby.london
Open Graph description is not detected on the main page of Thehouseoftoby. 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: