5.5 sec in total
80 ms
4.7 sec
652 ms
Visit toms.co.uk now to see the best up-to-date TOMS content for Greece and also check out these interesting facts you probably never knew about toms.co.uk
SHOES FOR MOVING FORWARD™ We've always been in business to improve lives. 1/3 of profits for grassroots good.
Visit toms.co.ukWe analyzed Toms.co.uk page load time and found that the first response time was 80 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
toms.co.uk performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value14.9 s
0/100
25%
Value11.3 s
5/100
10%
Value470 ms
61/100
30%
Value0
100/100
15%
Value14.6 s
8/100
10%
80 ms
178 ms
22 ms
274 ms
297 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 44% of them (23 requests) were addressed to the original Toms.co.uk, 54% (28 requests) were made to Media03.toms.com and 2% (1 request) were made to Js-agent.newrelic.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Media03.toms.com.
Page size can be reduced by 2.1 MB (51%)
4.2 MB
2.0 MB
In fact, the total size of Toms.co.uk main page is 4.2 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. 60% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 62.9 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. This page needs HTML code to be minified as it can gain 11.5 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 62.9 kB or 81% of the original size.
Potential reduce by 1.3 MB
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. Obviously, TOMS needs image optimization as it can save up to 1.3 MB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 362.6 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 362.6 kB or 79% of the original size.
Potential reduce by 422.6 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. Toms.co.uk needs all CSS files to be minified and compressed as it can save up to 422.6 kB or 87% of the original size.
Number of requests can be reduced by 10 (20%)
50
40
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TOMS. 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 as a result speed up the page load time.
toms.co.uk
80 ms
www.toms.co.uk
178 ms
foundation.css
22 ms
style.css
274 ms
modernizr.js
297 ms
jquery.js
34 ms
jquery.cookie.js
321 ms
foundation.min.js
27 ms
fastclick.js
314 ms
foundation.accordion.js
257 ms
foundation.orbit.js
257 ms
hoverIntent.js
319 ms
app.js
319 ms
endeca-auto-suggest.js
319 ms
GB_lang-flag.png
23 ms
CA_lang-flag.png
23 ms
FR_lang-flag.png
24 ms
DE_lang-flag.png
23 ms
NL_lang-flag.png
22 ms
US_lang-flag.png
24 ms
logo_trans.png
25 ms
mobile_nav_ico.png
23 ms
wovenstyles_UK.jpg
67 ms
UK-wks14-16-Nav-Giving.jpg
39 ms
wk10-UK-promo1c_1200x2400.jpg
497 ms
UK_brand-wk7.jpg
1033 ms
Shoes-symbol.png
23 ms
whiteBackground-Desktop.jpg
27 ms
wk8-UK-Promo2a_624x624.jpg
340 ms
wk8-UK-Promo2b_624x624.jpg
341 ms
UK-promo2c_624x624_new.jpg
341 ms
Bags-symbol-lft.png
168 ms
Bags-symbol-rt.png
169 ms
wk8-UK-Promo3a_624x624.jpg
342 ms
wk8-UK-Promo3b_624x624.jpg
344 ms
UK-promo4c_624x624_new.jpg
4091 ms
Eyewear-symbol-lft.png
340 ms
Eyewear-symbol-rt.png
341 ms
UK-promo3a_624x624_new.jpg
4057 ms
wk6-UK-promo3b_624x624.jpg
3545 ms
wk6-UK-promo3c_624x624.jpg
3468 ms
site_all_sprites.png
28 ms
proximanova-regular-toms.woff
56 ms
proximanova-semibold-toms.woff
148 ms
brandon_blk-toms.woff
316 ms
icomoon.svg
29 ms
footer_social_footer_bg.jpg
79 ms
social_sprite.png
79 ms
brandon_med-webfont.woff
79 ms
orbit_bnr_arrows.png
174 ms
HPGivingBlock-2400x1120.jpg
117 ms
nr-852.min.js
47 ms
toms.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
ARIA IDs are not unique
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
toms.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
toms.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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toms.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 Toms.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.
toms.co.uk
Open Graph description is not detected on the main page of TOMS. 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: