4.5 sec in total
348 ms
3.7 sec
393 ms
Visit redstones.co.uk now to see the best up-to-date Redstones content for United Kingdom and also check out these interesting facts you probably never knew about redstones.co.uk
Redstones estate agents and letting agents provides exceptional property sales and lettings. Fair pricing, local knowledge, personal service.
Visit redstones.co.ukWe analyzed Redstones.co.uk page load time and found that the first response time was 348 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
redstones.co.uk performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value11.4 s
0/100
25%
Value7.6 s
26/100
10%
Value320 ms
77/100
30%
Value1.027
2/100
15%
Value9.3 s
31/100
10%
348 ms
404 ms
641 ms
774 ms
183 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 53% of them (61 requests) were addressed to the original Redstones.co.uk, 7% (8 requests) were made to Apis.google.com and 6% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (838 ms) belongs to the original domain Redstones.co.uk.
Page size can be reduced by 1.1 MB (66%)
1.6 MB
552.3 kB
In fact, the total size of Redstones.co.uk main page is 1.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. Javascripts take 775.8 kB which makes up the majority of the site volume.
Potential reduce by 192.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 192.7 kB or 80% of the original size.
Potential reduce by 27.7 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. Redstones images are well optimized though.
Potential reduce by 568.0 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 568.0 kB or 73% of the original size.
Potential reduce by 266.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. Redstones.co.uk needs all CSS files to be minified and compressed as it can save up to 266.3 kB or 86% of the original size.
Number of requests can be reduced by 65 (65%)
100
35
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Redstones. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
redstones.co.uk
348 ms
www.redstones.co.uk
404 ms
default.aspx
641 ms
redstones_css.css
774 ms
tesa-responsive_nav.css
183 ms
flexnav.css
183 ms
responsive.css
374 ms
jquery.min.js
787 ms
flaunt.js
376 ms
jquery.flexnav.js
377 ms
common.js
469 ms
script.js
469 ms
jquery.validate.min.js
571 ms
jquery-ui.css
5 ms
jquery-ui.min.js
9 ms
jquery.tweet.js
470 ms
tmpl.js
569 ms
jquery.dependClass-0.1.js
569 ms
draggable-0.1.js
570 ms
jquery.slider.js
665 ms
jquery.sliderP.js
703 ms
jquery.sliderB.js
683 ms
jslider.css
683 ms
jquery.fancybox.js
835 ms
jquery.fancybox.css
838 ms
jquery.selectnav.js
837 ms
buttons.js
7 ms
WebResource.axd
667 ms
ScriptResource.axd
704 ms
ScriptResource.axd
705 ms
ScriptResource.axd
781 ms
FB.Share
11 ms
pinit.js
131 ms
Jquerypopup.css
647 ms
bootstrap.min.css
188 ms
ga.js
14 ms
pin_it_button.png
73 ms
platinum-logo.png
132 ms
CaptchaImage.axd
132 ms
wmVeryLarge_6775f1bf-ea3b-41d3-a83d-dca8c9588fbd.jpg
133 ms
wmVerylarge_122dda73-0269-4980-a6c2-601fb6ac72df.jpg
132 ms
wmVerylarge_a92f02b9-d687-453e-ac99-4b390f314df6.jpg
275 ms
wmVerylarge_8007537f-775d-4bc8-9099-9f1a33c877d0.jpg
131 ms
testimonial.jpg
275 ms
closebox.png
272 ms
2ec8d472-6bb4-4d3c-8fce-7290a7c9887a.png
273 ms
__utm.gif
34 ms
headerbg.gif
235 ms
menuicon.png
234 ms
icons-slice.png
444 ms
default.aspx
593 ms
bg-slider-txt.png
362 ms
transparentbg.png
362 ms
searchbg.png
353 ms
slider2.png
331 ms
plusone.js
192 ms
356 ms
widgets.js
158 ms
xd_arbiter.php
142 ms
xd_arbiter.php
153 ms
tweethead.png
384 ms
red-quotes.png
379 ms
pinit_main.js
506 ms
loading.gif
375 ms
arrow.png
366 ms
getAllAppDefault.esi
123 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
17 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
17 ms
cb=gapi.loaded_0
8 ms
cb=gapi.loaded_1
43 ms
fastbutton
101 ms
syndication
146 ms
346597742799364096
301 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
30 ms
postmessageRelay
65 ms
share_button.php
186 ms
getSegment.php
13 ms
checkOAuth.esi
28 ms
error-404.html
174 ms
t.dhj
16 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
19 ms
grlryt2bdKIyfMSOhzd1eA.woff
80 ms
t.dhj
20 ms
3193398744-postmessagerelay.js
58 ms
rpc:shindig_random.js
57 ms
cm
41 ms
s-3271.xgi
22 ms
cb=gapi.loaded_0
17 ms
16 ms
hbpix
25 ms
11 ms
xrefid.xgi
3 ms
pixel
19 ms
pixel
28 ms
qeKvIRsJabD.js
28 ms
LVx-xkvaJ0b.png
17 ms
error-404.html
94 ms
2981
59 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
2 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
5 ms
count.json
70 ms
error-404.html
93 ms
logo_normal.png
173 ms
error-404.html
218 ms
error-404.html
84 ms
jot.html
3 ms
error-404.html
91 ms
error-404.html
93 ms
error-404.html
109 ms
error-404.html
97 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
27 ms
buttons.ab966a004186897711de4a5ed256c924.css
15 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
3 ms
ui-bg_flat_75_ffffff_40x100.png
8 ms
wmveryLarge_d73ac5ec-79a8-4d90-9364-6710753219c0.jpg
221 ms
redstones.co.uk accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
ARIA IDs are not unique
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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
redstones.co.uk 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
General
Impact
Issue
Detected JavaScript libraries
redstones.co.uk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Redstones.co.uk 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 Redstones.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.
redstones.co.uk
Open Graph description is not detected on the main page of Redstones. 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: