Tools & Wizards About Us
travisvanslooten.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

travisvanslooten.com

Travis Van Slooten – Local SEO Consultant to Small Businesses

Page Load Speed

1.7 sec in total

First Response

152 ms

Resources Loaded

1.4 sec

Page Rendered

186 ms

travisvanslooten.com screenshot

About Website

Click here to check amazing Travis Van Slooten content. Otherwise, check out these important facts you probably never knew about travisvanslooten.com

Travis Van Slooten has been a full-time Internet Marketer since 2005. He's currently working with small businesses as a Local SEO consultant.

Visit travisvanslooten.com

Key Findings

We analyzed Travisvanslooten.com page load time and found that the first response time was 152 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

travisvanslooten.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

travisvanslooten.com

152 ms

21px.css

65 ms

css

22 ms

style.css

126 ms

widgets.js

12 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 24% of them (8 requests) were addressed to the original Travisvanslooten.com, 18% (6 requests) were made to Apis.google.com and 12% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (913 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.9 kB (16%)

Content Size

480.7 kB

After Optimization

401.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Travisvanslooten.com main page is 480.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 315.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 77.8 kB

  • Original 99.1 kB
  • After minification 98.6 kB
  • After compression 21.3 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 77.8 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 228 B

  • Original 64.1 kB
  • After minification 63.9 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. Travis Van Slooten images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 394 B

  • Original 315.1 kB
  • After minification 315.0 kB
  • After compression 314.7 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

-19%

Potential reduce by 454 B

  • Original 2.4 kB
  • After minification 2.4 kB
  • After compression 1.9 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. Travisvanslooten.com needs all CSS files to be minified and compressed as it can save up to 454 B or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (45%)

Requests Now

29

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

travisvanslooten.com

travisvanslooten.com

152 ms

21px.css

21px.css

65 ms

css

css

22 ms

style.css

style.css

126 ms

widgets.js

widgets.js

12 ms

in.js

in.js

10 ms

pinit.js

pinit.js

20 ms

linkedin.png

linkedin.png

183 ms

twitter.png

twitter.png

182 ms

googleplus.png

googleplus.png

183 ms

emailme.png

emailme.png

181 ms

all.js

all.js

23 ms

all.js

all.js

59 ms

PinExt.png

PinExt.png

6 ms

plusone.js

plusone.js

43 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

41 ms

travis.jpg

travis.jpg

191 ms

98 ms

pinit_main.js

pinit_main.js

38 ms

settings

settings

102 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

37 ms

fastbutton

fastbutton

34 ms

count.json

count.json

58 ms

postmessageRelay

postmessageRelay

34 ms

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

14 ms

developers.google.com

developers.google.com

913 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

4 ms

2254111616-postmessagerelay.js

2254111616-postmessagerelay.js

24 ms

rpc:shindig_random.js

rpc:shindig_random.js

8 ms

embeds

embeds

23 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

12 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

Accessibility Review

travisvanslooten.com accessibility score

91

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

travisvanslooten.com best practices score

75

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

travisvanslooten.com SEO score

77

Search Engine Optimization Advices

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

travisvanslooten.com

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