4.9 sec in total
1.9 sec
2.8 sec
158 ms
Welcome to whatsthatthen.com homepage info - get ready to check What SThat Then best content right away, or after learning these important things about whatsthatthen.com
Unique gifts, homewares & indulgences.
Visit whatsthatthen.comWe analyzed Whatsthatthen.com page load time and found that the first response time was 1.9 sec and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
whatsthatthen.com performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value3.1 s
75/100
25%
Value10.0 s
9/100
10%
Value0 ms
100/100
30%
Value0.164
72/100
15%
Value1.9 s
100/100
10%
1892 ms
48 ms
95 ms
94 ms
487 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 76% of them (28 requests) were addressed to the original Whatsthatthen.com, 22% (8 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Whatsthatthen.com.
Page size can be reduced by 232.8 kB (38%)
604.9 kB
372.1 kB
In fact, the total size of Whatsthatthen.com main page is 604.9 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. 35% of websites need less resources to load. Images take 308.0 kB which makes up the majority of the site volume.
Potential reduce by 22.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 22.4 kB or 71% of the original size.
Potential reduce by 11.2 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. What SThat Then images are well optimized though.
Potential reduce by 88.9 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 88.9 kB or 65% of the original size.
Potential reduce by 110.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. Whatsthatthen.com needs all CSS files to be minified and compressed as it can save up to 110.3 kB or 85% of the original size.
Number of requests can be reduced by 17 (65%)
26
9
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What SThat Then. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
whatsthatthen.com
1892 ms
woocommerce.css
48 ms
style.css
95 ms
layout.css
94 ms
whatsthatthen.com
487 ms
comment-reply.min.js
119 ms
jquery.js
159 ms
third-party.js
109 ms
jquery.flexslider.min.js
169 ms
general.js
142 ms
css
23 ms
shortcodes.css
190 ms
custom.css
181 ms
add-to-cart.min.js
201 ms
jquery.blockUI.min.js
204 ms
woocommerce.min.js
215 ms
jquery.cookie.min.js
227 ms
cart-fragments.min.js
236 ms
jquery.placeholder.min.js
246 ms
feedback.js
249 ms
bkgrnd.jpg
52 ms
WTT-header4.png
95 ms
WTT-logo3.png
99 ms
thumb.php
347 ms
thumb.php
307 ms
thumb.php
276 ms
woothemes.png
111 ms
fontawesome-webfont.woff
182 ms
PIPMHY90P7jtyjpXuZ2cLD8E0i7KZn-EPnyo3HZu7kw.woff
35 ms
lILlYDvubYemzYzN7GbLkHhCUOGz7vYGh680lGh-uXM.woff
43 ms
LKf8nhXsWg5ybwEGXk8UBQ.woff
70 ms
0XxGQsSc1g4rdRdjJKZrNBsxEYwM7FgeyaSgU71cLG0.woff
70 ms
QABk9IxT-LFTJ_dQzv7xpIbN6UDyHWBl620a-IRfuBk.woff
60 ms
sDRi4fY9bOiJUbgq53yZCfesZW2xOQ-xsNqO47m55DA.woff
61 ms
03aPdn7fFF3H6ngCgAlQzBsxEYwM7FgeyaSgU71cLG0.woff
61 ms
Foydq9xJp--nfYIx2TBz9QFhaRv2pGgT5Kf0An0s4MM.woff
68 ms
websymbols-regular-webfont.woff
60 ms
whatsthatthen.com accessibility score
whatsthatthen.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
whatsthatthen.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatsthatthen.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 Whatsthatthen.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.
whatsthatthen.com
Open Graph description is not detected on the main page of What SThat Then. 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: