3.8 sec in total
1.1 sec
2.5 sec
263 ms
Visit trinityii.com now to see the best up-to-date TRINITY Ii content for United States and also check out these interesting facts you probably never knew about trinityii.com
Shop powered by PrestaShop
Visit trinityii.comWe analyzed Trinityii.com page load time and found that the first response time was 1.1 sec and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
trinityii.com performance score
name
value
score
weighting
Value3.4 s
39/100
10%
Value3.5 s
64/100
25%
Value3.8 s
84/100
10%
Value430 ms
65/100
30%
Value0.024
100/100
15%
Value7.3 s
50/100
10%
1070 ms
438 ms
90 ms
92 ms
94 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Trinityii.com, 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Shop.trinityii.com.
Page size can be reduced by 1.1 MB (59%)
1.9 MB
783.3 kB
In fact, the total size of Trinityii.com main page is 1.9 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. 55% of websites need less resources to load. Javascripts take 665.0 kB which makes up the majority of the site volume.
Potential reduce by 95.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. This page needs HTML code to be minified as it can gain 15.7 kB, which is 14% 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 95.4 kB or 87% of the original size.
Potential reduce by 63.5 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. TRINITY Ii images are well optimized though.
Potential reduce by 514.8 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 514.8 kB or 77% of the original size.
Potential reduce by 467.9 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. Trinityii.com needs all CSS files to be minified and compressed as it can save up to 467.9 kB or 89% of the original size.
Number of requests can be reduced by 48 (63%)
76
28
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TRINITY Ii. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
index.php
1070 ms
global.css
438 ms
uniform.default.css
90 ms
product_list.css
92 ms
blockcart.css
94 ms
jquery.bxslider.css
94 ms
blockcategories.css
132 ms
blocknewsletter.css
134 ms
blocksearch.css
136 ms
jquery.autocomplete.css
136 ms
blockwishlist.css
166 ms
styles.css
174 ms
owl.carousel.css
178 ms
owl.theme.css
179 ms
typo.css
181 ms
hooks.css
208 ms
blockuserinfo.css
216 ms
productcomments.css
221 ms
jquery.fancybox.css
223 ms
leocustomajax.css
224 ms
jquery-1.11.0.min.js
292 ms
jquery-migrate-1.2.1.min.js
256 ms
jquery.easing.js
264 ms
tools.js
264 ms
global.js
265 ms
10-bootstrap.min.js
300 ms
15-jquery.total-storage.min.js
308 ms
15-jquery.uniform-modified.js
353 ms
products-comparison.js
310 ms
ajax-cart.js
335 ms
jquery.scrollTo.js
343 ms
jquery.serialScroll.js
353 ms
jquery.bxslider.js
355 ms
treeManagement.js
379 ms
blocknewsletter.js
387 ms
jquery.autocomplete.js
399 ms
css
23 ms
responsive.css
326 ms
font-awesome.min.css
325 ms
test33.css
395 ms
1custom.css
395 ms
blocksearch.js
366 ms
ajax-wishlist.js
358 ms
owl.carousel.js
369 ms
script.js
354 ms
jquery.themepunch.enablelog.js
354 ms
jquery.themepunch.revolution.js
452 ms
jquery.themepunch.tools.min.js
372 ms
index.js
321 ms
jquery.fancybox.js
341 ms
leocustomajax.js
338 ms
icon-cart-2.png
67 ms
logo-2.png
68 ms
trinity-store-logo.jpg
70 ms
KitchenCart_Homepage_900.jpg
242 ms
ShelvingRack_HomePage_900.jpg
242 ms
OutdoorLiving_Homepage_1000.jpg
324 ms
eco_64x64.png
91 ms
nsf_64x64.png
92 ms
commercial_64x64.png
91 ms
787-home_default.jpg
237 ms
539-home_default.jpg
238 ms
636-home_default.jpg
237 ms
642-home_default.jpg
238 ms
647-home_default.jpg
239 ms
651-home_default.jpg
239 ms
661-home_default.jpg
241 ms
766-home_default.jpg
241 ms
974-home_default.jpg
242 ms
980-home_default.jpg
242 ms
b-before.jpg.jpg
243 ms
timer.png
279 ms
fontawesome-webfont.woff
277 ms
icon-cart-2.PNG
228 ms
loader.gif
227 ms
large_left.png
227 ms
large_right.png
254 ms
bg-product.jpg
255 ms
border-name.png
254 ms
trinityii.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.
trinityii.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
Browser errors were logged to the console
Page has valid source maps
trinityii.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
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 Trinityii.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 Trinityii.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.
trinityii.com
Open Graph description is not detected on the main page of TRINITY Ii. 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: