2.3 sec in total
213 ms
1.4 sec
656 ms
Click here to check amazing Moors Bus content. Otherwise, check out these important facts you probably never knew about moorsbus.org
Moorsbus operates a bus network servicing the North York Moors National Park in summer.
Visit moorsbus.orgWe analyzed Moorsbus.org page load time and found that the first response time was 213 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
moorsbus.org performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value7.0 s
6/100
25%
Value2.5 s
97/100
10%
Value220 ms
87/100
30%
Value0.03
100/100
15%
Value6.5 s
59/100
10%
213 ms
102 ms
196 ms
293 ms
26 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 71% of them (24 requests) were addressed to the original Moorsbus.org, 21% (7 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (863 ms) belongs to the original domain Moorsbus.org.
Page size can be reduced by 117.4 kB (3%)
3.8 MB
3.7 MB
In fact, the total size of Moorsbus.org main page is 3.8 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. 40% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 88.6 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 23.0 kB, which is 23% 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 88.6 kB or 88% 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. Moors Bus images are well optimized though.
Potential reduce by 465 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 4.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. Moorsbus.org needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 16% of the original size.
Number of requests can be reduced by 3 (12%)
26
23
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moors Bus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
moorsbus.org
213 ms
normalize.css
102 ms
webflow.css
196 ms
moorsbus-b.webflow.css
293 ms
webfont.js
26 ms
jquery-3.5.1.min.dc5e7f18c8.js
23 ms
webflow.js
620 ms
css
28 ms
moorsbus-logo-small.png
200 ms
pound-coins.jpg
290 ms
helmsley-castle.jpg
289 ms
MoorRewards.jpg
468 ms
Walk-and-Ride.jpg
573 ms
friends-of-moorsbus.jpg
400 ms
volunteering.jpg
392 ms
Slide-Rosedale.jpg
575 ms
moorsbus-logo-3.png
482 ms
Slide-Rosedale-2.jpg
499 ms
Slide-Towards-Ramsdale.jpg
598 ms
Slide-Commondale.jpg
750 ms
Slide-Moortop.jpg
582 ms
moorsbus-top-bus.jpg
603 ms
north-york-moors-map.jpg
863 ms
sutton-bank-small.jpg
675 ms
M5-small.jpg
682 ms
Helen-Gundry.jpg
798 ms
sutton-bank-homepage.jpg
808 ms
KFOmCnqEu92Fr1Mu4mxM.woff
8 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
15 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
16 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
16 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
16 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
17 ms
KFOkCnqEu92Fr1Mu51xIIzQ.woff
72 ms
moorsbus.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
moorsbus.org 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
moorsbus.org 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moorsbus.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Moorsbus.org 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.
moorsbus.org
Open Graph data is detected on the main page of Moors Bus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: