2.3 sec in total
231 ms
1.6 sec
450 ms
Welcome to williamcastle.co.uk homepage info - get ready to check William Castle best content right away, or after learning these important things about williamcastle.co.uk
Introduction to the work of English instrument maker, William Castle, his violins, violas and cellos.
Visit williamcastle.co.ukWe analyzed Williamcastle.co.uk page load time and found that the first response time was 231 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.
williamcastle.co.uk performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value2.9 s
81/100
25%
Value4.7 s
69/100
10%
Value280 ms
80/100
30%
Value0.078
95/100
15%
Value6.6 s
57/100
10%
231 ms
387 ms
18 ms
46 ms
67 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 56% of them (20 requests) were addressed to the original Williamcastle.co.uk, 22% (8 requests) were made to Williamcastle.wpengine.com and 14% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (837 ms) relates to the external source Williamcastle.wpengine.com.
Page size can be reduced by 230.3 kB (13%)
1.8 MB
1.6 MB
In fact, the total size of Williamcastle.co.uk main page is 1.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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 229.4 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 229.4 kB or 87% of the original size.
Potential reduce by 81 B
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. William Castle images are well optimized though.
Potential reduce by 213 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 554 B
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. Williamcastle.co.uk has all CSS files already compressed.
Number of requests can be reduced by 15 (54%)
28
13
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of William Castle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
williamcastle.co.uk
231 ms
williamcastle.co.uk
387 ms
wp_head.css
18 ms
css
46 ms
style.min.css
67 ms
style.css
21 ms
gtf5ysc.js
135 ms
js
80 ms
style.css
34 ms
style.css
34 ms
jquery.min.js
43 ms
jquery-migrate.min.js
43 ms
scripts.min.js
94 ms
smoothscroll.js
74 ms
frontend-bundle.min.js
51 ms
common.js
72 ms
wp_footer.js
73 ms
William-Logo_7-04.svg
333 ms
final-header2.jpg
27 ms
et-divi-dynamic-74-late.css
18 ms
subscribe-loader.gif
148 ms
MOBILE-05359.jpg
497 ms
P1120234-lighter.jpg
837 ms
varnishing-a-cello.jpg
562 ms
2-PICT0230.jpg
655 ms
Violas-by-William-Castle-OPT.jpg
332 ms
william2.jpg
666 ms
William_Castle_Logo-OPT.jpg
421 ms
d
155 ms
modules.woff
31 ms
modules.woff
123 ms
d
165 ms
d
58 ms
d
90 ms
p.gif
45 ms
style.min.css
21 ms
williamcastle.co.uk 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.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
williamcastle.co.uk 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
Issues were logged in the Issues panel in Chrome Devtools
williamcastle.co.uk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Williamcastle.co.uk 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 Williamcastle.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.
williamcastle.co.uk
Open Graph data is detected on the main page of William Castle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: