Tools & Wizards About Us
garandguy.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

garandguy.com

Home - The Garand Guy

Page Load Speed

8.1 sec in total

First Response

1.1 sec

Resources Loaded

6.8 sec

Page Rendered

199 ms

garandguy.com screenshot

About Website

Welcome to garandguy.com homepage info - get ready to check Garand Guy best content for Canada right away, or after learning these important things about garandguy.com

Visit garandguy.com

Key Findings

We analyzed Garandguy.com page load time and found that the first response time was 1.1 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

garandguy.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value4,350 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.146

77/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

garandguy.com

1117 ms

index.css

175 ms

sbi-styles.min.css

179 ms

style.min.css

238 ms

wc-blocks-vendors-style.css

177 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 86% of them (107 requests) were addressed to the original Garandguy.com, 2% (3 requests) were made to Fonts.googleapis.com and 2% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Garandguy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 668.7 kB (28%)

Content Size

2.4 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Garandguy.com main page is 2.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. 60% of websites need less resources to load. CSS take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 124.7 kB

  • Original 153.4 kB
  • After minification 149.8 kB
  • After compression 28.7 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 124.7 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 19.7 kB

  • Original 270.0 kB
  • After minification 250.3 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. Garand Guy images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 235.0 kB

  • Original 871.7 kB
  • After minification 871.1 kB
  • After compression 636.6 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 235.0 kB or 27% of the original size.

CSS Optimization

-26%

Potential reduce by 289.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 808.8 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. Garandguy.com needs all CSS files to be minified and compressed as it can save up to 289.3 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 97 (84%)

Requests Now

115

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Garand Guy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 44 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

garandguy.com

garandguy.com

1117 ms

index.css

index.css

175 ms

sbi-styles.min.css

sbi-styles.min.css

179 ms

style.min.css

style.min.css

238 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

177 ms

wc-blocks-style.css

wc-blocks-style.css

305 ms

tooltipster.css

tooltipster.css

298 ms

tooltipster-light.css

tooltipster-light.css

352 ms

animations.css

animations.css

350 ms

booked.css

booked.css

372 ms

styles.css

styles.css

661 ms

settings.css

settings.css

473 ms

fontello.css

fontello.css

484 ms

trx_addons_icons-embedded.css

trx_addons_icons-embedded.css

710 ms

swiper.min.css

swiper.min.css

547 ms

magnific-popup.min.css

magnific-popup.min.css

548 ms

trx_addons.css

trx_addons.css

776 ms

trx_addons.animation.css

trx_addons.animation.css

675 ms

trx_socials_icons.css

trx_socials_icons.css

725 ms

instagram.css

instagram.css

724 ms

woocommerce-layout.css

woocommerce-layout.css

834 ms

woocommerce.css

woocommerce.css

911 ms

frontend-style.css

frontend-style.css

886 ms

all.css

all.css

37 ms

js_composer.min.css

js_composer.min.css

1023 ms

stylesheet.css

stylesheet.css

906 ms

css

css

42 ms

fontello-embedded.css

fontello-embedded.css

1186 ms

style.css

style.css

1139 ms

__colors.css

__colors.css

1316 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

1101 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

1100 ms

trx_addons.responsive.css

trx_addons.responsive.css

1207 ms

responsive.css

responsive.css

1363 ms

v4-shims.css

v4-shims.css

31 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1286 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1365 ms

wp-polyfill.min.js

wp-polyfill.min.js

1433 ms

hooks.min.js

hooks.min.js

1426 ms

w.js

w.js

22 ms

css

css

17 ms

css

css

24 ms

widget.js

widget.js

683 ms

animate.min.css

animate.min.css

1388 ms

elementor-icons.min.css

elementor-icons.min.css

1340 ms

custom-frontend.min.css

custom-frontend.min.css

1425 ms

swiper.min.css

swiper.min.css

1384 ms

rs6.css

rs6.css

1429 ms

elegro-style.css

elegro-style.css

1326 ms

jquery.min.js

jquery.min.js

1432 ms

jquery-migrate.min.js

jquery-migrate.min.js

1340 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1394 ms

add-to-cart.min.js

add-to-cart.min.js

1405 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

1330 ms

frontend-functions.js

frontend-functions.js

1371 ms

core.min.js

core.min.js

1324 ms

datepicker.min.js

datepicker.min.js

1436 ms

spin.min.js

spin.min.js

1267 ms

spin.jquery.js

spin.jquery.js

1277 ms

jquery.tooltipster.min.js

jquery.tooltipster.min.js

1277 ms

functions.js

functions.js

1470 ms

index.js

index.js

1320 ms

trx_addons.debug.css

trx_addons.debug.css

1312 ms

index.js

index.js

1427 ms

rbtools.min.js

rbtools.min.js

1487 ms

rs6.min.js

rs6.min.js

1565 ms

swiper.jquery.min.js

swiper.jquery.min.js

1458 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1403 ms

trx_addons.js

trx_addons.js

1458 ms

js.cookie.min.js

js.cookie.min.js

1395 ms

woocommerce.min.js

woocommerce.min.js

1392 ms

functions.js

functions.js

1377 ms

superfish.min.js

superfish.min.js

1410 ms

__scripts.js

__scripts.js

1433 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1445 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

1371 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

1373 ms

js_composer_front.min.js

js_composer_front.min.js

1317 ms

cart-fragments.min.js

cart-fragments.min.js

1366 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

1408 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

1413 ms

underscore-before.js

underscore-before.js

1369 ms

underscore.min.js

underscore.min.js

1324 ms

underscore-after.js

underscore-after.js

1360 ms

vc-waypoints.min.js

vc-waypoints.min.js

1316 ms

vc_grid.min.js

vc_grid.min.js

1392 ms

tabs.min.js

tabs.min.js

1353 ms

effect.min.js

effect.min.js

1364 ms

effect-fade.min.js

effect-fade.min.js

1326 ms

webpack.runtime.min.js

webpack.runtime.min.js

1354 ms

frontend-modules.min.js

frontend-modules.min.js

1367 ms

waypoints.min.js

waypoints.min.js

1385 ms

frontend.min.js

frontend.min.js

1411 ms

chart.min.js

chart.min.js

1344 ms

elegro-script.js

elegro-script.js

1309 ms

elegro-ga.js

elegro-ga.js

1640 ms

g.gif

g.gif

229 ms

Black-and-Green-Illustrated-Skull-Army-Esport-Team-Logo-7.png

Black-and-Green-Illustrated-Skull-Army-Esport-Team-Logo-7.png

1664 ms

dummy.png

dummy.png

1596 ms

titilliumweb-regular-webfont.woff

titilliumweb-regular-webfont.woff

1703 ms

N+6gaV3IxODy2bWFDYGFxcAlBwqBwAA

N+6gaV3IxODy2bWFDYGFxcAlBwqBwAA

28 ms

DewXAiKGIjI2Nf5AbGnRwMHAzJBRsZWJ02MTAyaIEYm7mYGDkgLD4GMIvNaRfTAaA0J5DN7rSLwQHCZmZw2ajC2BEYscGhI2Ijc4rLRjUQbxdHAwMji0NHckgESEkkEGzmYWLk0drB+L91A0vvRiYGFwAMdiP0AAA=

DewXAiKGIjI2Nf5AbGnRwMHAzJBRsZWJ02MTAyaIEYm7mYGDkgLD4GMIvNaRfTAaA0J5DN7rSLwQHCZmZw2ajC2BEYscGhI2Ijc4rLRjUQbxdHAwMji0NHckgESEkkEGzmYWLk0drB+L91A0vvRiYGFwAMdiP0AAA=

27 ms

font

font

190 ms

titilliumweb-light-webfont.woff

titilliumweb-light-webfont.woff

1635 ms

titilliumweb-extralight-webfont.woff

titilliumweb-extralight-webfont.woff

1567 ms

titilliumweb-semibold-webfont.woff

titilliumweb-semibold-webfont.woff

1569 ms

titilliumweb-bold-webfont.woff

titilliumweb-bold-webfont.woff

1577 ms

titilliumweb-black-webfont.woff

titilliumweb-black-webfont.woff

1602 ms

fontello.svg

fontello.svg

1793 ms

trx_addons_icons.svg

trx_addons_icons.svg

1707 ms

Number-4-M1-with-Krieger-Match-Barrel-and-New-Walnut-Wood-with-new-or-like-new-components-in-30-06-or-308-362x362.jpg

Number-4-M1-with-Krieger-Match-Barrel-and-New-Walnut-Wood-with-new-or-like-new-components-in-30-06-or-308-362x362.jpg

1561 ms

Number-2-M1-with-USGI-barrel-and-new-Walnut-Stock-and-Handguards-362x362.jpg

Number-2-M1-with-USGI-barrel-and-new-Walnut-Stock-and-Handguards-362x362.jpg

1624 ms

Copy-of-Number-2-M1-with-USGI-barrel-and-new-Walnut-Stock-and-Handguards-1-362x362.png

Copy-of-Number-2-M1-with-USGI-barrel-and-new-Walnut-Stock-and-Handguards-1-362x362.png

1632 ms

iframe_api

iframe_api

43 ms

Number-5-Tanker-with-new-Citadel-barrel-in-30-06-or-308-1-362x362.png

Number-5-Tanker-with-new-Citadel-barrel-in-30-06-or-308-1-362x362.png

1593 ms

Copy-of-Number-2-M1-with-USGI-barrel-and-new-Walnut-Stock-and-Handguards-362x362.png

Copy-of-Number-2-M1-with-USGI-barrel-and-new-Walnut-Stock-and-Handguards-362x362.png

1638 ms

2-150x150.png

2-150x150.png

1641 ms

www-widgetapi.js

www-widgetapi.js

5 ms

analytics.js

analytics.js

177 ms

font

font

135 ms

font

font

147 ms

garandguy.com

garandguy.com

1179 ms

collect

collect

14 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

184 ms

Accessibility Review

garandguy.com accessibility score

66

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

garandguy.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

garandguy.com SEO score

78

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Garandguy.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 Garandguy.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.

Social Sharing Optimization

garandguy.com

Open Graph description is not detected on the main page of Garand Guy. 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: