14.3 sec in total
508 ms
13.3 sec
462 ms
Click here to check amazing Sawyer content for United States. Otherwise, check out these important facts you probably never knew about sawyer.com
We believe in protecting and fostering an outdoor community of all backgrounds and enthusiasms.
Visit sawyer.comWe analyzed Sawyer.com page load time and found that the first response time was 508 ms and then it took 13.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
sawyer.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value3.7 s
58/100
25%
Value5.6 s
53/100
10%
Value370 ms
71/100
30%
Value0.033
100/100
15%
Value7.6 s
46/100
10%
508 ms
110 ms
128 ms
85 ms
142 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 70% of them (48 requests) were addressed to the original Sawyer.com, 10% (7 requests) were made to Apis.google.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (11.5 sec) relates to the external source Freegeoip.net.
Page size can be reduced by 457.4 kB (15%)
3.1 MB
2.7 MB
In fact, the total size of Sawyer.com main page is 3.1 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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 38.5 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 38.5 kB or 78% of the original size.
Potential reduce by 40.7 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. Sawyer images are well optimized though.
Potential reduce by 192.0 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 192.0 kB or 60% of the original size.
Potential reduce by 186.2 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. Sawyer.com needs all CSS files to be minified and compressed as it can save up to 186.2 kB or 88% of the original size.
Number of requests can be reduced by 27 (42%)
65
38
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sawyer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
sawyer.com
508 ms
front.controller.css.php
110 ms
style.css
128 ms
mp-hubspot.css
85 ms
jquery.js
142 ms
jquery-migrate.min.js
88 ms
css
59 ms
conversion_async.js
63 ms
front.controller.js.php
196 ms
script.min.js
138 ms
mp-hubspot.min.js
137 ms
wp-embed.min.js
179 ms
wp-emoji-release.min.js
59 ms
analytics.js
311 ms
platform.js
336 ms
icons-social.png
264 ms
sawyer.png
260 ms
search.png
260 ms
wkyo.png
285 ms
water.png
260 ms
repellant.png
275 ms
spf.png
282 ms
firstaid.png
283 ms
mountain.jpg
360 ms
logo-amazon.png
282 ms
logo-walmart.png
312 ms
logo-rei2016.png
312 ms
logo-cabelas.png
311 ms
a_aegypti_0-200x150.png
329 ms
Screen-Shot-2015-09-23-at-4.27.08-PM-200x150.png
393 ms
Consumer-Reports-Picaridin-200x150.png
394 ms
Jen-at-Springer-200x150.jpg
342 ms
logo-footer-sawyer.png
343 ms
sawyer-international-small.png
390 ms
product-search.png
391 ms
11471 ms
1901983.js
512 ms
Overview-1240x493-1.jpg
299 ms
Picaridin-bkgd1-1240x493.jpg
232 ms
mini2016.jpg
431 ms
goi-1240x493.jpg
263 ms
liberia2016.jpg
315 ms
sawyer-u-bkgd-1240x493.jpg
241 ms
Picaridin-top.png
350 ms
Slider-mini-filter10.png
330 ms
goi1.png
402 ms
Sawyer-International8.png
351 ms
sawyer-u-text1.png
521 ms
arrow-left.png
354 ms
arrow-right.png
382 ms
slider-loader.gif
378 ms
processing.gif
383 ms
leaguegothic-regular-webfont.woff
404 ms
s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff
104 ms
EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff
117 ms
leaguegothic-italic-webfont.woff
398 ms
collect
20 ms
collect
91 ms
cb=gapi.loaded_0
39 ms
cb=gapi.loaded_1
61 ms
fastbutton
119 ms
ga-audiences
54 ms
postmessageRelay
65 ms
cb=gapi.loaded_0
20 ms
cb=gapi.loaded_1
18 ms
api.js
61 ms
core:rpc:shindig.random:shindig.sha1.js
84 ms
2536007149-postmessagerelay.js
66 ms
11227 ms
sawyer.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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
sawyer.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
sawyer.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 Sawyer.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 Sawyer.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.
sawyer.com
Open Graph data is detected on the main page of Sawyer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: