2.8 sec in total
732 ms
1.8 sec
274 ms
Visit williamthomas.com now to see the best up-to-date William Thomas content and also check out these interesting facts you probably never knew about williamthomas.com
Our award-winning design team specializes in handcrafted rings, earrings, pendants and necklaces loaded with diamonds, gemstones & self expression.
Visit williamthomas.comWe analyzed Williamthomas.com page load time and found that the first response time was 732 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.
williamthomas.com performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value15.7 s
0/100
25%
Value17.2 s
0/100
10%
Value14,730 ms
0/100
30%
Value0.083
94/100
15%
Value27.5 s
0/100
10%
732 ms
83 ms
164 ms
106 ms
104 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 89% of them (33 requests) were addressed to the original Williamthomas.com, 11% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (732 ms) belongs to the original domain Williamthomas.com.
Page size can be reduced by 327.6 kB (34%)
961.2 kB
633.6 kB
In fact, the total size of Williamthomas.com main page is 961.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 522.2 kB which makes up the majority of the site volume.
Potential reduce by 16.5 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 16.5 kB or 75% of the original size.
Potential reduce by 8.8 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. William Thomas images are well optimized though.
Potential reduce by 180.3 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 180.3 kB or 66% of the original size.
Potential reduce by 122.0 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. Williamthomas.com needs all CSS files to be minified and compressed as it can save up to 122.0 kB or 85% of the original size.
Number of requests can be reduced by 16 (44%)
36
20
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of William Thomas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.williamthomas.com
732 ms
style.css
83 ms
formidablepro.css
164 ms
ssbp.min.css
106 ms
wpgmza_style.css
104 ms
jquery.js
210 ms
jquery-migrate.min.js
114 ms
easy-columns.css
137 ms
script.js
188 ms
flexslider.css
177 ms
public.css
176 ms
comment-reply.min.js
185 ms
ssbp_standard.min.js
276 ms
ssbp_email.min.js
276 ms
wp-embed.min.js
271 ms
jquery.flexslider-min.js
320 ms
wp-emoji-release.min.js
176 ms
ga.js
44 ms
analytics.js
35 ms
Bottom_texture.jpg
197 ms
page_gl.png
194 ms
header.jpg
188 ms
header-object.png
195 ms
nav.png
187 ms
menuitem.png
201 ms
postbullets.png
201 ms
Home-pg-blue-ring.jpg
203 ms
Home-pag-necklaces.jpg
205 ms
Home-pg-bracelet.jpg
203 ms
Home-pg-purple-ring.jpg
205 ms
home_pg_diamond_earrings.jpg
258 ms
Home-pg-gold.jpg
268 ms
multi-diamond-ring.jpg
310 ms
simple-share-buttons-logo-white.png
253 ms
__utm.gif
139 ms
collect
130 ms
bg_direction_nav.png
55 ms
williamthomas.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.
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
Image elements do not have [alt] attributes
williamthomas.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
williamthomas.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Williamthomas.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 Williamthomas.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.
williamthomas.com
Open Graph description is not detected on the main page of William Thomas. 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: