25.5 sec in total
1.5 sec
23.5 sec
427 ms
Click here to check amazing Simonwall content. Otherwise, check out these important facts you probably never knew about simonwall.com
Stephanie Macnab
Visit simonwall.comWe analyzed Simonwall.com page load time and found that the first response time was 1.5 sec and then it took 23.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
simonwall.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value7.5 s
4/100
25%
Value7.5 s
26/100
10%
Value560 ms
53/100
30%
Value0.001
100/100
15%
Value13.0 s
13/100
10%
1545 ms
141 ms
271 ms
269 ms
2361 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 90% of them (37 requests) were addressed to the original Simonwall.com, 7% (3 requests) were made to Powering2.expertagent.co.uk and 2% (1 request) were made to Preview.expertagent.co.uk. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Preview.expertagent.co.uk.
Page size can be reduced by 144.8 kB (5%)
2.9 MB
2.8 MB
In fact, the total size of Simonwall.com main page is 2.9 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. 25% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 26.0 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 26.0 kB or 85% of the original size.
Potential reduce by 26.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. Simonwall images are well optimized though.
Potential reduce by 70.8 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 70.8 kB or 67% of the original size.
Potential reduce by 21.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. Simonwall.com needs all CSS files to be minified and compressed as it can save up to 21.3 kB or 78% of the original size.
Number of requests can be reduced by 9 (24%)
38
29
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Simonwall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
simonwall.com
1545 ms
style.css
141 ms
style_Jslider.css
271 ms
style_slideShow.css
269 ms
jscript_00jquery-1.5.min.js
2361 ms
jscript_10jquery.html.js
273 ms
jscript_form_valid.js
270 ms
jscript_slideShow.js
290 ms
jscript_slider.js
380 ms
eawc.css
379 ms
eawc.js
380 ms
sw_signature_web0001.jpg
19551 ms
sw_Head_shot_crop.jpg
2806 ms
pow.aspx
346 ms
Compass_Survey_Logo_overspill_web.jpg
839 ms
bg.jpg
184 ms
leftbg.jpg
294 ms
logo-trans.png
1053 ms
arrow-open.png
184 ms
search.jpg
295 ms
librk.jpg
186 ms
1.jpg
1760 ms
2.jpg
1789 ms
3.jpg
635 ms
Formby.jpg
2005 ms
Southport_front_2.jpg
2050 ms
southport_front.jpg
1423 ms
southport.jpg
2499 ms
box1bg.jpg
1583 ms
read.jpg
1714 ms
box2bg.jpg
1798 ms
follow-us-on.gif
1885 ms
facebook-icon.gif
1885 ms
twitter-icon.gif
1883 ms
linked-icon.gif
2012 ms
ARLA-logo.jpg
2029 ms
om.jpg
2043 ms
om1.jpg
2213 ms
oMs.jpg
2215 ms
pow.aspx
135 ms
eapowering2.css
184 ms
simonwall.com 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
Links do not have a discernible name
simonwall.com 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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
simonwall.com 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
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Simonwall.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 Simonwall.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
simonwall.com
Open Graph description is not detected on the main page of Simonwall. 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: