3.4 sec in total
500 ms
2.4 sec
537 ms
Visit pretorian.com now to see the best up-to-date Pretorian content for Brazil and also check out these interesting facts you probably never knew about pretorian.com
Conheça a nossa linha completa de produtos: Equipamentos, Luvas, Acessórios, Bonés, Suplementos, Vestuário, Calçados, Aparadores, Kits e muito mais!
Visit pretorian.comWe analyzed Pretorian.com page load time and found that the first response time was 500 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pretorian.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value4.6 s
35/100
25%
Value10.3 s
8/100
10%
Value4,060 ms
1/100
30%
Value0.039
99/100
15%
Value23.1 s
1/100
10%
500 ms
49 ms
102 ms
58 ms
59 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 58% of them (26 requests) were addressed to the original Pretorian.com, 7% (3 requests) were made to Cdn.shopify.com and 4% (2 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (779 ms) belongs to the original domain Pretorian.com.
Page size can be reduced by 744.3 kB (53%)
1.4 MB
667.8 kB
In fact, the total size of Pretorian.com main page is 1.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. 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. HTML takes 850.9 kB which makes up the majority of the site volume.
Potential reduce by 738.3 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 738.3 kB or 87% of the original size.
Potential reduce by 0 B
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. Pretorian images are well optimized though.
Potential reduce by 838 B
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 5.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. Pretorian.com has all CSS files already compressed.
Number of requests can be reduced by 35 (85%)
41
6
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pretorian. 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 11 to 1 for CSS and as a result speed up the page load time.
www.pretorian.com
500 ms
jcjpyk4i36
49 ms
gtm.js
102 ms
css
58 ms
vendor.min.css
59 ms
theme-styles.css
76 ms
theme-styles-responsive.css
62 ms
theme-settings.css
74 ms
footer-09.css
75 ms
product-surfup.css
94 ms
fonts.css
98 ms
custom.css
96 ms
unique-scripts-head.js
105 ms
preloads.js
103 ms
load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js
93 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
94 ms
styles.css
110 ms
scripts.js
213 ms
jquery-3.6.0.min.js
30 ms
slick.min.js
40 ms
component-toolbar-mobile.css
192 ms
unique-scripts-footer.js
286 ms
custom.js
284 ms
template7.js
192 ms
clarity.js
7 ms
trekkie.storefront.6feac1db1e2c7d84269967dcaefdee0618af51f6.min.js
196 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
194 ms
shopify-boomerang-1.0.0.min.js
196 ms
FX1_1850x.jpg
98 ms
fontawesome-webfont.woff
708 ms
k.js
66 ms
no-image-2048-5e88c1b20e087fb7bbe9a3771824e743c244f437e4f8ba93bbf7b11b53f7824c_1024x1024.gif
39 ms
seal-review.min.js
60 ms
star-rating.css
145 ms
bundle.js
77 ms
sp-whatsapp-app-tabs.js
373 ms
lo.js
38 ms
loader.js
295 ms
instafeed-0db7afa830537423959420be0a6e60a1.js
159 ms
thankyou.js
95 ms
42984_1714774403.js
71 ms
fontawesome-webfont.ttf
779 ms
lo.legacy.js
55 ms
c.gif
21 ms
b02989ca
282 ms
pretorian.com 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 input fields do not have accessible names
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
pretorian.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
pretorian.com SEO score
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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pretorian.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Pretorian.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.
pretorian.com
Open Graph data is detected on the main page of Pretorian. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: