Tools & Wizards About Us

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

blog.scottevest.com

SCOTTeVEST: It’s not Rocket Science. It’s Pocket Science!

Page Load Speed

8.5 sec in total

First Response

1.2 sec

Resources Loaded

4.2 sec

Page Rendered

3.1 sec

About Website

Click here to check amazing Blog SCOTTeVEST content for United States. Otherwise, check out these important facts you probably never knew about blog.scottevest.com

It's not Rocket Science. It's Pocket Science! We started with vests and now we use our Pocket Science in jackets, hoodies and so much more!

Visit blog.scottevest.com

Key Findings

We analyzed Blog.scottevest.com page load time and found that the first response time was 1.2 sec and then it took 7.3 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

blog.scottevest.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value30.7 s

0/100

10%

TBT (Total Blocking Time)

Value11,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value44.1 s

0/100

10%

Network Requests Diagram

www.scottevest.com

1239 ms

global.js

60 ms

jquery.js

89 ms

fancybox.js

58 ms

slick.js

57 ms

Our browser made a total of 175 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Blog.scottevest.com, 7% (12 requests) were made to Fonts.gstatic.com and 5% (9 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Scottevest.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 676.6 kB (15%)

Content Size

4.6 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 480.4 kB

  • Original 602.3 kB
  • After minification 538.8 kB
  • After compression 121.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. This page needs HTML code to be minified as it can gain 63.5 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 480.4 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 100.6 kB

  • Original 2.9 MB
  • After minification 2.8 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. Blog SCOTTeVEST images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 92.5 kB

  • Original 887.6 kB
  • After minification 887.4 kB
  • After compression 795.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 3.1 kB

  • Original 170.6 kB
  • After minification 170.6 kB
  • After compression 167.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. Blog.scottevest.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 88 (58%)

Requests Now

152

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

blog.scottevest.com accessibility score

63

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-*] attributes do not match their roles

High

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

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

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.

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

blog.scottevest.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

High

Missing source maps for large first-party JavaScript

SEO Factors

blog.scottevest.com SEO score

74

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Blog.scottevest.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 Blog.scottevest.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

Open Graph data is detected on the main page of Blog SCOTTeVEST. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: