Tools & Wizards About Us
strungmag.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

strungmag.com

Strung Sporting Journal – Fish, Hunt, Eat, Conserve

Page Load Speed

9.1 sec in total

First Response

929 ms

Resources Loaded

7.2 sec

Page Rendered

995 ms

strungmag.com screenshot

About Website

Click here to check amazing Strung Mag content. Otherwise, check out these important facts you probably never knew about strungmag.com

Visit strungmag.com

Key Findings

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

Performance Metrics

strungmag.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value32.5 s

0/100

25%

SI (Speed Index)

Value27.1 s

0/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value37.0 s

0/100

10%

Network Requests Diagram

strungmag.com

929 ms

blocks-checkout.css

175 ms

style.min.css

266 ms

styles.css

340 ms

nectar-slider.css

113 ms

Our browser made a total of 140 requests to load all elements on the main page. We found that 94% of them (131 requests) were addressed to the original Strungmag.com, 3% (4 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Strungmag.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 491.5 kB (5%)

Content Size

9.7 MB

After Optimization

9.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Strungmag.com main page is 9.7 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. Only a small number of websites need less resources to load. Images take 8.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 90.1 kB

  • Original 111.0 kB
  • After minification 107.5 kB
  • After compression 20.9 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 90.1 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 197.0 kB

  • Original 8.9 MB
  • After minification 8.7 MB

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. Strung Mag images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 114.9 kB

  • Original 443.1 kB
  • After minification 443.1 kB
  • After compression 328.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 114.9 kB or 26% of the original size.

CSS Optimization

-31%

Potential reduce by 89.5 kB

  • Original 284.3 kB
  • After minification 284.3 kB
  • After compression 194.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. Strungmag.com needs all CSS files to be minified and compressed as it can save up to 89.5 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 104 (78%)

Requests Now

134

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

strungmag.com

strungmag.com

929 ms

blocks-checkout.css

blocks-checkout.css

175 ms

style.min.css

style.min.css

266 ms

styles.css

styles.css

340 ms

nectar-slider.css

nectar-slider.css

113 ms

style.css

style.css

116 ms

woocommerce-layout.css

woocommerce-layout.css

121 ms

woocommerce.css

woocommerce.css

292 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

201 ms

grid-system.css

grid-system.css

246 ms

style.css

style.css

479 ms

header-layout-centered-logo-between-menu.css

header-layout-centered-logo-between-menu.css

297 ms

element-fancy-box.css

element-fancy-box.css

335 ms

element-recent-posts.css

element-recent-posts.css

436 ms

css

css

44 ms

responsive.css

responsive.css

394 ms

product-style-classic.css

product-style-classic.css

378 ms

woocommerce.css

woocommerce.css

470 ms

skin-original.css

skin-original.css

496 ms

menu-dynamic.css

menu-dynamic.css

486 ms

widget-nectar-posts.css

widget-nectar-posts.css

491 ms

js_composer.min.css

js_composer.min.css

610 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

593 ms

um-modal.min.css

um-modal.min.css

641 ms

jquery-ui.min.css

jquery-ui.min.css

649 ms

tipsy.min.css

tipsy.min.css

586 ms

um-raty.min.css

um-raty.min.css

677 ms

fonticons-ii.min.css

fonticons-ii.min.css

699 ms

fonticons-fa.min.css

fonticons-fa.min.css

695 ms

select2.min.css

select2.min.css

775 ms

um-fileupload.min.css

um-fileupload.min.css

825 ms

default.min.css

default.min.css

830 ms

default.date.min.css

default.date.min.css

753 ms

default.time.min.css

default.time.min.css

788 ms

common.min.css

common.min.css

779 ms

um-responsive.min.css

um-responsive.min.css

846 ms

um-styles.min.css

um-styles.min.css

943 ms

css

css

26 ms

w.js

w.js

22 ms

js

js

71 ms

cropper.min.css

cropper.min.css

861 ms

um-profile.min.css

um-profile.min.css

776 ms

um-account.min.css

um-account.min.css

885 ms

um-misc.min.css

um-misc.min.css

951 ms

um-old-default.min.css

um-old-default.min.css

773 ms

woocommerce-non-critical.css

woocommerce-non-critical.css

758 ms

magnific.css

magnific.css

726 ms

core.css

core.css

772 ms

simple-dropdown.css

simple-dropdown.css

825 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

793 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

752 ms

wp-polyfill.min.js

wp-polyfill.min.js

834 ms

hooks.min.js

hooks.min.js

1061 ms

jquery.min.js

jquery.min.js

795 ms

jquery-migrate.min.js

jquery-migrate.min.js

725 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

715 ms

add-to-cart.min.js

add-to-cart.min.js

799 ms

js.cookie.min.js

js.cookie.min.js

772 ms

woocommerce.min.js

woocommerce.min.js

846 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

779 ms

um-gdpr.min.js

um-gdpr.min.js

754 ms

email-decode.min.js

email-decode.min.js

660 ms

index.js

index.js

751 ms

index.js

index.js

713 ms

anime.min.js

anime.min.js

876 ms

nectar-slider.js

nectar-slider.js

1052 ms

salient-social.js

salient-social.js

731 ms

sourcebuster.min.js

sourcebuster.min.js

824 ms

order-attribution.min.js

order-attribution.min.js

770 ms

jquery.easing.min.js

jquery.easing.min.js

801 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

797 ms

priority.js

priority.js

847 ms

nectar-slider-priority.js

nectar-slider-priority.js

753 ms

transit.min.js

transit.min.js

805 ms

waypoints.js

waypoints.js

787 ms

imagesLoaded.min.js

imagesLoaded.min.js

769 ms

hoverintent.min.js

hoverintent.min.js

842 ms

magnific.js

magnific.js

791 ms

superfish.js

superfish.js

779 ms

init.js

init.js

772 ms

touchswipe.min.js

touchswipe.min.js

869 ms

tracking.min.js

tracking.min.js

844 ms

underscore.min.js

underscore.min.js

855 ms

wp-util.min.js

wp-util.min.js

802 ms

i18n.min.js

i18n.min.js

751 ms

tipsy.min.js

tipsy.min.js

753 ms

picker.min.js

picker.min.js

859 ms

picker.date.min.js

picker.date.min.js

818 ms

picker.time.min.js

picker.time.min.js

710 ms

common.min.js

common.min.js

739 ms

cropper.min.js

cropper.min.js

820 ms

common-frontend.min.js

common-frontend.min.js

804 ms

um-modal.min.js

um-modal.min.js

815 ms

jquery-form.min.js

jquery-form.min.js

733 ms

fileupload.js

fileupload.js

861 ms

um-functions.min.js

um-functions.min.js

729 ms

um-responsive.min.js

um-responsive.min.js

768 ms

um-conditional.min.js

um-conditional.min.js

742 ms

select2.full.min.js

select2.full.min.js

944 ms

en.js

en.js

719 ms

g.gif

g.gif

88 ms

um-raty.min.js

um-raty.min.js

632 ms

um-scripts.min.js

um-scripts.min.js

708 ms

um-profile.min.js

um-profile.min.js

671 ms

um-account.min.js

um-account.min.js

740 ms

cart-fragments.min.js

cart-fragments.min.js

663 ms

js_composer_front.min.js

js_composer_front.min.js

750 ms

Strung-Logo-1.png

Strung-Logo-1.png

723 ms

Magazine-Spread-1.png

Magazine-Spread-1.png

789 ms

Winter-Wheat-3-copy-1-600x357.jpg

Winter-Wheat-3-copy-1-600x357.jpg

786 ms

ptarmigan-hunting-in-alsaka-2-strung-magazine.jpg

ptarmigan-hunting-in-alsaka-2-strung-magazine.jpg

1109 ms

font

font

84 ms

icomoon.woff

icomoon.woff

1017 ms

font

font

160 ms

font

font

89 ms

font

font

159 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

831 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

835 ms

strung-sporting-journal-upland-birds-2-600x403.jpg

strung-sporting-journal-upland-birds-2-600x403.jpg

832 ms

Strung-Magazine-fishing-for-carp-1.jpg

Strung-Magazine-fishing-for-carp-1.jpg

928 ms

pie2-copy-140x140.jpg

pie2-copy-140x140.jpg

930 ms

watefowl-magazine-6-140x140.jpg

watefowl-magazine-6-140x140.jpg

823 ms

Strung-magazine-is-a-fly-fishing-magazine-4-140x140.jpg

Strung-magazine-is-a-fly-fishing-magazine-4-140x140.jpg

821 ms

Sheep-hunt-in-Alaska-1.jpg

Sheep-hunt-in-Alaska-1.jpg

911 ms

winterwaterfowl-hunting-strung-magazine-140x140.jpg

winterwaterfowl-hunting-strung-magazine-140x140.jpg

911 ms

apple-app-store.png

apple-app-store.png

866 ms

google-play.png

google-play.png

853 ms

Strung-Website-0082-scaled.jpg

Strung-Website-0082-scaled.jpg

854 ms

Strung-Website-4245-scaled.jpg

Strung-Website-4245-scaled.jpg

941 ms

Strung-Website-1030-scaled.jpg

Strung-Website-1030-scaled.jpg

876 ms

Strung-Website-2532-scaled.jpg

Strung-Website-2532-scaled.jpg

1310 ms

grid.png

grid.png

778 ms

big-game-hunting-magazine-red-stag-1.jpg

big-game-hunting-magazine-red-stag-1.jpg

843 ms

Strung-Website-6604-scaled.jpg

Strung-Website-6604-scaled.jpg

767 ms

Magazine-Spread-3.jpg

Magazine-Spread-3.jpg

366 ms

Wingshooting-scaled.jpg

Wingshooting-scaled.jpg

489 ms

food-scaled.jpg

food-scaled.jpg

441 ms

strungmag.com

strungmag.com

3443 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

276 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

176 ms

Accessibility Review

strungmag.com accessibility score

80

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

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

strungmag.com best practices score

92

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

SEO Factors

strungmag.com SEO score

84

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

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 Strungmag.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 Strungmag.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

strungmag.com

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