4.2 sec in total
1 sec
2.1 sec
1.1 sec
Welcome to toms.ie homepage info - get ready to check TOMS best content right away, or after learning these important things about toms.ie
SHOES FOR MOVING FORWARD™ We've always been in business to improve lives. 1/3 of profits for grassroots good.
Visit toms.ieWe analyzed Toms.ie page load time and found that the first response time was 1 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
toms.ie performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value9.7 s
0/100
25%
Value10.0 s
9/100
10%
Value820 ms
35/100
30%
Value0
100/100
15%
Value9.9 s
27/100
10%
1046 ms
28 ms
39 ms
55 ms
288 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Toms.ie, 5% (3 requests) were made to E.cquotient.com and 3% (2 requests) were made to Optanon.blob.core.windows.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Toms.com.
Page size can be reduced by 358.4 kB (15%)
2.4 MB
2.0 MB
In fact, the total size of Toms.ie main page is 2.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 340.6 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 340.6 kB or 81% of the original size.
Potential reduce by 6.4 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. TOMS images are well optimized though.
Potential reduce by 11.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 232 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. Toms.ie has all CSS files already compressed.
Number of requests can be reduced by 16 (28%)
57
41
The browser has sent 57 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 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
uk
1046 ms
bootstrap.css
28 ms
global.css
39 ms
homePage.css
55 ms
de434457-e5f0-400f-9114-dfee6eda3b8f.js
288 ms
main.js
64 ms
lib.js
403 ms
10043107-10044414.js
122 ms
ui.js
53 ms
ad.js
32 ms
dwanalytics-22.2.js
36 ms
dwac-21.7.js
46 ms
gretel.min.js
47 ms
applepay.js
50 ms
optanon.css
71 ms
jquery-3.3.1.min.js
15 ms
NavigationTile_Ws_520x650-Alp.jpg
29 ms
NavigationTile_Ws_520x650_Constance.jpg
30 ms
NavigationTile_Ws_520x650-Lola.jpg
30 ms
NavigationTile_Ms_520x650_Palomar.jpg
28 ms
NavigationTile_Ms_520x650_Ezra.jpg
31 ms
NavigationTile_Ms_520x650_AlpFWD.jpg
29 ms
0501_nav_impact_mham_d_394x296.jpg
78 ms
0109_nav_impact_learn_more_d_394x296.jpg
79 ms
IMPACT_NAV2_UK.jpg
50 ms
0109_nav_impact_purpose_d_394x296.jpg
46 ms
0109_nav_impact_planet_d_394x296.jpg
77 ms
0109_nav_impact_people_d_394x296.jpg
149 ms
EOSS-24_DiscountIncrease_Hero1_m_640x525_UK.gif
80 ms
DiscountIncrease_Category_Promo1A_171x78_Gradient.jpg
80 ms
EMEA_WK03_Hero2_m_750x525_v1.jpg
79 ms
new.svg
80 ms
10020666-S.jpg
82 ms
10020224-S.jpg
82 ms
best-seller.svg
83 ms
10018925-S.jpg
95 ms
10020250-S.jpg
93 ms
exclusive.svg
93 ms
10016338-S.jpg
97 ms
water-resistant.svg
95 ms
10016893-S.jpg
96 ms
10020298-S.jpg
150 ms
EMEA_WK03_4L_m_750x663_v1.jpg
99 ms
EMEA_Web_WK03_3L_m_750x600.jpg
148 ms
10020771-S.jpg
149 ms
10020716-F.jpg
148 ms
HPStoriesTile_750x843_Winter_Boots.jpg
220 ms
HPStories_Women_Exclusives_750x843.gif
155 ms
HPStories_Cosy_Collection_750x843.png
153 ms
HP_Stories_Mens_Boots_FH23.gif
221 ms
HPStories_Alpargata_750x843.jpg
152 ms
HPStories_Black_Collection_750x843.jpg
151 ms
0125_toms_impact_mark_v2.png
130 ms
degular-regular.woff
194 ms
degular-medium.woff
194 ms
degular-semibold.woff
194 ms
degular-bold.woff
194 ms
degular-black.woff
194 ms
tomsicons.woff
36 ms
product-to-product-two
88 ms
product-to-product-two
120 ms
products-in-all-categories-withoutsalegc
90 ms
CQRecomm-Start
139 ms
CQRecomm-Start
111 ms
toms.ie 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
toms.ie 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
toms.ie 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.ie 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.ie 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.ie
Open Graph data is detected on the main page of TOMS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: