8.2 sec in total
192 ms
7.6 sec
400 ms
Click here to check amazing Treohans content. Otherwise, check out these important facts you probably never knew about treohans.com
At Treohans we stock a huge range of discounted homeware and housing supplies. Order for delivery, click and collect or visit our Clapham store
Visit treohans.comWe analyzed Treohans.com page load time and found that the first response time was 192 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
treohans.com performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value11.5 s
0/100
25%
Value13.2 s
2/100
10%
Value2,100 ms
7/100
30%
Value0.016
100/100
15%
Value15.9 s
6/100
10%
192 ms
5537 ms
235 ms
254 ms
253 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 69% of them (79 requests) were addressed to the original Treohans.com, 26% (30 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Treohans.com.
Page size can be reduced by 269.8 kB (16%)
1.7 MB
1.4 MB
In fact, the total size of Treohans.com main page is 1.7 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. 75% 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 680.5 kB which makes up the majority of the site volume.
Potential reduce by 240.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. 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 240.9 kB or 84% of the original size.
Potential reduce by 20.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. Treohans images are well optimized though.
Potential reduce by 7.7 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 1.1 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. Treohans.com has all CSS files already compressed.
Number of requests can be reduced by 71 (87%)
82
11
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Treohans. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
treohans.com
192 ms
treohans.com
5537 ms
blocks-checkout.css
235 ms
divi.css
254 ms
mediaelementplayer-legacy.min.css
253 ms
wp-mediaelement.min.css
257 ms
magnific_popup.css
246 ms
animate.css
258 ms
woocommerce-layout.css
437 ms
woocommerce.css
443 ms
common.min.css
448 ms
wppopups-base.css
447 ms
style.min.css
447 ms
jquery.min.js
502 ms
jquery-migrate.min.js
440 ms
jquery.blockUI.min.js
457 ms
add-to-cart.min.js
446 ms
js.cookie.min.js
458 ms
woocommerce.min.js
522 ms
s-202405.js
12 ms
et-core-unified-7.min.css
461 ms
wc-blocks.css
526 ms
wp-polyfill-inert.min.js
526 ms
regenerator-runtime.min.js
527 ms
wp-polyfill.min.js
532 ms
hooks.min.js
535 ms
wppopups.js
550 ms
sourcebuster.min.js
550 ms
order-attribution.min.js
552 ms
react.min.js
551 ms
deprecated.min.js
611 ms
dom.min.js
615 ms
react-dom.min.js
714 ms
escape-html.min.js
637 ms
element.min.js
639 ms
is-shallow-equal.min.js
638 ms
i18n.min.js
692 ms
keycodes.min.js
697 ms
api.js
61 ms
e-202405.js
1 ms
priority-queue.min.js
719 ms
compose.min.js
742 ms
private-apis.min.js
729 ms
redux-routine.min.js
724 ms
data.min.js
725 ms
lodash.min.js
723 ms
wc-blocks-registry.js
720 ms
url.min.js
622 ms
api-fetch.min.js
615 ms
wc-settings.js
610 ms
data-controls.min.js
610 ms
html-entities.min.js
540 ms
notices.min.js
526 ms
wc-blocks-middleware.js
602 ms
wc-blocks-data.js
603 ms
dom-ready.min.js
605 ms
embed
28 ms
a11y.min.js
546 ms
primitives.min.js
540 ms
js
105 ms
warning.min.js
520 ms
et-divi-dynamic-tb-64-7-late.css
547 ms
blocks-components.js
583 ms
KFOlCnqEu92Fr1MmSU5fChc-.woff
29 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
37 ms
KFOkCnqEu92Fr1MmgVxGIzQ.woff
38 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
35 ms
KFOmCnqEu92Fr1Mu7GxM.woff
38 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
38 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
37 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
39 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
52 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
51 ms
KFOlCnqEu92Fr1MmYUtfChc-.woff
51 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
52 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
53 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
53 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
55 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
55 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
55 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
55 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
60 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
61 ms
blocks-checkout.js
580 ms
order-attribution-blocks.min.js
578 ms
common.min.js
575 ms
scripts.min.js
613 ms
es6-promise.auto.min.js
606 ms
recaptcha.js
606 ms
jquery.fitvids.js
611 ms
jquery.mobile.js
551 ms
frontend-bundle.min.js
575 ms
common.js
618 ms
frontend.min.js
618 ms
modules.woff
638 ms
New-logo-580w.png
584 ms
PNG-IMG-Square.png
579 ms
Screenshot-2021-10-20-at-20.21.57.png
776 ms
E-com-payment-logo-420w.png
621 ms
man-machine-hardware-store-smiling-mid-aged-man-utensils-hardware-store-seller-professional_t20_ywwNLO.jpg
653 ms
stylish-double-bathroom-PPRAS74.jpg
585 ms
industry-steel-tool-equipment-pliers-screwdriver-repair-tools-hardware-power-tools_t20_6wn1d9.jpg
903 ms
New-logo-580w-300x68.png
518 ms
recaptcha__de.js
27 ms
woocommerce-smallscreen.css
84 ms
treohans.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
treohans.com 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
treohans.com 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 Treohans.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 Treohans.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.
treohans.com
Open Graph data is detected on the main page of Treohans. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: