8.2 sec in total
2.1 sec
5.9 sec
171 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 2.1 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
pretorian.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value8.1 s
2/100
25%
Value9.1 s
13/100
10%
Value2,410 ms
5/100
30%
Value0.001
100/100
15%
Value17.6 s
4/100
10%
2120 ms
276 ms
689 ms
277 ms
278 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 82% of them (55 requests) were addressed to the original Pretorian.com, 6% (4 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Pretorian.com.
Page size can be reduced by 457.1 kB (29%)
1.6 MB
1.1 MB
In fact, the total size of Pretorian.com main page is 1.6 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. 45% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 18.8 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 18.8 kB or 77% of the original size.
Potential reduce by 28.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. Pretorian images are well optimized though.
Potential reduce by 231.3 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 231.3 kB or 71% of the original size.
Potential reduce by 178.4 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 needs all CSS files to be minified and compressed as it can save up to 178.4 kB or 84% of the original size.
Number of requests can be reduced by 30 (47%)
64
34
The browser has sent 64 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 17 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.pretorian.com
2120 ms
flexslider.css
276 ms
bootstrap.css
689 ms
bootstrap-responsive.css
277 ms
component.css
278 ms
theme.css
283 ms
style.css
551 ms
css
24 ms
css
36 ms
tubepress.css
412 ms
youtube.css
414 ms
simply-instagram.css
425 ms
simply-instagram-prettyPhoto.css
710 ms
tooltipster.css
709 ms
styles.css
709 ms
jquery.js
1109 ms
jquery-migrate.min.js
822 ms
tubepress.js
960 ms
wordpress-ajax.js
961 ms
jquery.tooltipster.min.js
1105 ms
simply-instagram-jquery.prettyPhoto.js
1104 ms
jquery.min.js
23 ms
jquery.flexslider.js
1117 ms
bootstrap.min.js
969 ms
jquery.infinitescroll.min.js
1110 ms
jquery.form.min.js
1109 ms
scripts.js
1130 ms
wp-embed.min.js
1131 ms
wp-emoji-release.min.js
605 ms
header-container.png
257 ms
header-bg.png
258 ms
logo.png
258 ms
search.png
260 ms
pt.png
260 ms
en.png
260 ms
es.png
364 ms
PR_980x305_banner_luvas_.jpg
642 ms
pretorian_open_site_1.png
1055 ms
PT_triceps_banner_web_950_264_carol_dias.jpg
927 ms
leiamais.png
370 ms
challenge-sem-fundo-240x200.png
509 ms
PR_intagram_luvas_rosa-240x200.jpg
501 ms
F9A6836-240x200.jpg
507 ms
6_PT_triceps_instagram_carol_dias-240x200.jpg
639 ms
news-arrow.png
644 ms
news-img.jpg
649 ms
subscribe.png
775 ms
facebook-n.png
776 ms
twitter-n.png
781 ms
rss-n.png
787 ms
insta-n.png
912 ms
footer-arrow.png
913 ms
widgets.js
22 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
20 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
115 ms
ajax-loader.gif
776 ms
slide-nav-hover.png
780 ms
slide-nav.png
900 ms
nav-left.png
902 ms
nav-right.png
905 ms
flexslider-icon.woff
823 ms
syndication
89 ms
438049717050564608
112 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
4 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
5 ms
_Rc6DpWc_normal.jpg
131 ms
jot
25 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
PT
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 matches the claimed 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 description is not detected on the main page of Pretorian. 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: