Tools & Wizards About Us
trimnellshouse.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

trimnellshouse.com

Trimnells House Holiday Lettings – Holiday Lettings Guest Accommodation

Page Load Speed

13.9 sec in total

First Response

4 sec

Resources Loaded

9 sec

Page Rendered

885 ms

trimnellshouse.com screenshot

About Website

Welcome to trimnellshouse.com homepage info - get ready to check Trimnells House best content right away, or after learning these important things about trimnellshouse.com

Visit trimnellshouse.com

Key Findings

We analyzed Trimnellshouse.com page load time and found that the first response time was 4 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

trimnellshouse.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value24.9 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value1,620 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.173

69/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

trimnellshouse.com

3980 ms

jquery.min.js

33 ms

style.min.css

269 ms

style.min.css

182 ms

style.min.css

274 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 89% of them (129 requests) were addressed to the original Trimnellshouse.com, 8% (11 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Trimnellshouse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 851.3 kB (4%)

Content Size

20.4 MB

After Optimization

19.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trimnellshouse.com main page is 20.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. Only a small number of websites need less resources to load. Images take 18.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 292.3 kB

  • Original 344.1 kB
  • After minification 333.4 kB
  • After compression 51.8 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 292.3 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 316.0 kB

  • Original 18.8 MB
  • After minification 18.5 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. Trimnells House images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 157.2 kB

  • Original 903.5 kB
  • After minification 902.1 kB
  • After compression 746.2 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 157.2 kB or 17% of the original size.

CSS Optimization

-28%

Potential reduce by 85.8 kB

  • Original 304.1 kB
  • After minification 228.1 kB
  • After compression 218.3 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. Trimnellshouse.com needs all CSS files to be minified and compressed as it can save up to 85.8 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 93 (73%)

Requests Now

128

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trimnellshouse.com

trimnellshouse.com

3980 ms

jquery.min.js

jquery.min.js

33 ms

style.min.css

style.min.css

269 ms

style.min.css

style.min.css

182 ms

style.min.css

style.min.css

274 ms

style.min.css

style.min.css

174 ms

style.min.css

style.min.css

175 ms

style.min.css

style.min.css

264 ms

blocks.style.build.css

blocks.style.build.css

263 ms

styles.css

styles.css

280 ms

wonderplugincarouselengine.css

wonderplugincarouselengine.css

300 ms

form_style.css

form_style.css

355 ms

bootstrap.css

bootstrap.css

445 ms

bootstrap-theme.css

bootstrap-theme.css

352 ms

style.css

style.css

460 ms

my_media.css

my_media.css

361 ms

jquery-ui.min.css

jquery-ui.min.css

404 ms

daterangepicker.css

daterangepicker.css

439 ms

leaflet.css

leaflet.css

440 ms

MarkerCluster.css

MarkerCluster.css

456 ms

MarkerCluster.Default.css

MarkerCluster.Default.css

507 ms

css

css

47 ms

fontello.css

fontello.css

525 ms

font-awesome.min.css

font-awesome.min.css

526 ms

all.css

all.css

531 ms

elementor-icons.min.css

elementor-icons.min.css

537 ms

frontend.min.css

frontend.min.css

557 ms

swiper.min.css

swiper.min.css

612 ms

post-319.css

post-319.css

612 ms

frontend.min.css

frontend.min.css

724 ms

global.css

global.css

621 ms

post-35362.css

post-35362.css

626 ms

Defaults.css

Defaults.css

643 ms

css

css

45 ms

jquery.min.js

jquery.min.js

762 ms

jquery-migrate.min.js

jquery-migrate.min.js

700 ms

wonderplugincarouselskins.js

wonderplugincarouselskins.js

710 ms

wonderplugincarousel.js

wonderplugincarousel.js

817 ms

modernizr.custom.62456.js

modernizr.custom.62456.js

776 ms

post-35694.css

post-35694.css

601 ms

fontawesome.min.css

fontawesome.min.css

619 ms

solid.min.css

solid.min.css

622 ms

post-35697.css

post-35697.css

714 ms

post-35700.css

post-35700.css

646 ms

post-35702.css

post-35702.css

647 ms

animations.min.css

animations.min.css

634 ms

rs6.css

rs6.css

680 ms

index.js

index.js

678 ms

index.js

index.js

658 ms

rbtools.min.js

rbtools.min.js

882 ms

rs6.min.js

rs6.min.js

984 ms

core.min.js

core.min.js

842 ms

mouse.min.js

mouse.min.js

822 ms

slider.min.js

slider.min.js

787 ms

datepicker.min.js

datepicker.min.js

785 ms

menu.min.js

menu.min.js

779 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

880 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

850 ms

wp-polyfill.min.js

wp-polyfill.min.js

907 ms

dom-ready.min.js

dom-ready.min.js

816 ms

hooks.min.js

hooks.min.js

811 ms

i18n.min.js

i18n.min.js

865 ms

a11y.min.js

a11y.min.js

861 ms

autocomplete.min.js

autocomplete.min.js

836 ms

slick.min.js

slick.min.js

793 ms

bootstrap.min.js

bootstrap.min.js

825 ms

jquery.viewport.mini.js

jquery.viewport.mini.js

863 ms

placeholders.min.js

placeholders.min.js

858 ms

slideout.min.js

slideout.min.js

847 ms

dense.js

dense.js

793 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

788 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

780 ms

latinise.min_.js

latinise.min_.js

797 ms

moment.min.js

moment.min.js

805 ms

daterangepicker.js

daterangepicker.js

801 ms

places.js@1.13.0

places.js@1.13.0

944 ms

algoliasearch.min.js

algoliasearch.min.js

782 ms

leaflet.js

leaflet.js

761 ms

leaflet.markercluster.js

leaflet.markercluster.js

762 ms

datepicker-en-GB.js

datepicker-en-GB.js

766 ms

mapfunctions.js

mapfunctions.js

768 ms

ajaxcalls.js

ajaxcalls.js

733 ms

maps_base.js

maps_base.js

880 ms

google_map_code.js

google_map_code.js

873 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

59 ms

KFOmCnqEu92Fr1Mu7GxP.ttf

KFOmCnqEu92Fr1Mu7GxP.ttf

60 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

276 ms

KFOlCnqEu92Fr1MmEU9fChc9.ttf

KFOlCnqEu92Fr1MmEU9fChc9.ttf

276 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

279 ms

KFOlCnqEu92Fr1MmSU5fChc9.ttf

KFOlCnqEu92Fr1MmSU5fChc9.ttf

338 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

278 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

337 ms

KFOlCnqEu92Fr1MmWUlfChc9.ttf

KFOlCnqEu92Fr1MmWUlfChc9.ttf

337 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

338 ms

KFOlCnqEu92Fr1MmYUtfChc9.ttf

KFOlCnqEu92Fr1MmYUtfChc9.ttf

338 ms

control.js

control.js

877 ms

chart.bundle.min.js

chart.bundle.min.js

709 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

609 ms

webpack.runtime.min.js

webpack.runtime.min.js

613 ms

frontend-modules.min.js

frontend-modules.min.js

623 ms

frontend.min.js

frontend.min.js

718 ms

waypoints.min.js

waypoints.min.js

713 ms

frontend.min.js

frontend.min.js

611 ms

elements-handlers.min.js

elements-handlers.min.js

611 ms

fa-solid-900.woff

fa-solid-900.woff

634 ms

fa-regular-400.woff

fa-regular-400.woff

871 ms

fontello.woff

fontello.woff

867 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

813 ms

logo.png

logo.png

810 ms

Winphone-036.jpg

Winphone-036.jpg

810 ms

image00085.jpeg

image00085.jpeg

1388 ms

image00075-scaled.jpeg

image00075-scaled.jpeg

1720 ms

image00068-1-scaled.jpeg

image00068-1-scaled.jpeg

1097 ms

image00187-scaled.jpeg

image00187-scaled.jpeg

954 ms

image00199-3-scaled.jpeg

image00199-3-scaled.jpeg

1729 ms

image00182-1-scaled.jpeg

image00182-1-scaled.jpeg

915 ms

image00203-scaled.jpeg

image00203-scaled.jpeg

1085 ms

image00167-2.jpeg

image00167-2.jpeg

1252 ms

image00160-scaled.jpeg

image00160-scaled.jpeg

1202 ms

image00156-scaled.jpeg

image00156-scaled.jpeg

1096 ms

Winphone-034.jpg

Winphone-034.jpg

1172 ms

trim10.jpeg

trim10.jpeg

1257 ms

Winphone-033.jpg

Winphone-033.jpg

1263 ms

Pic-holiday-020-400x314.jpg

Pic-holiday-020-400x314.jpg

1188 ms

Pic-holiday-039-400x314.jpg

Pic-holiday-039-400x314.jpg

1216 ms

trimnells-house-garden.jpg

trimnells-house-garden.jpg

1281 ms

kithen.jpeg

kithen.jpeg

1271 ms

trimnells-house-exterior.jpg

trimnells-house-exterior.jpg

1298 ms

STA70699.jpg

STA70699.jpg

2842 ms

kitchen_5.jpeg

kitchen_5.jpeg

1214 ms

image00098-scaled.jpeg

image00098-scaled.jpeg

1227 ms

image00123-400x314.jpeg

image00123-400x314.jpeg

1252 ms

image00093-400x314.jpeg

image00093-400x314.jpeg

1294 ms

image00117-400x314.jpeg

image00117-400x314.jpeg

1322 ms

image00115-400x314.jpeg

image00115-400x314.jpeg

1339 ms

Pic-holiday-022.jpg

Pic-holiday-022.jpg

1292 ms

Roman_Baths_in_Bath_Spa_England_-_July_2006-scaled.jpg

Roman_Baths_in_Bath_Spa_England_-_July_2006-scaled.jpg

3219 ms

Bath-Spa.jpg

Bath-Spa.jpg

1321 ms

bath-city-boat-trips.jpg

bath-city-boat-trips.jpg

1324 ms

trimnellshouse.com

trimnellshouse.com

2989 ms

froogaloop2.min.js

froogaloop2.min.js

1327 ms

iframe_api

iframe_api

231 ms

mhfontello.css

mhfontello.css

1119 ms

hoveroverlay-64-64-5.png

hoveroverlay-64-64-5.png

1168 ms

www-widgetapi.js

www-widgetapi.js

6 ms

Accessibility Review

trimnellshouse.com accessibility score

87

Accessibility Issues

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.

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

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

High

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

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

trimnellshouse.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

trimnellshouse.com SEO score

93

Search Engine Optimization Advices

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

trimnellshouse.com

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