Tools & Wizards About Us
jeffreybarr.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

jeffreybarr.com

Jeffrey Barr Resume

Page Load Speed

1.1 sec in total

First Response

120 ms

Resources Loaded

776 ms

Page Rendered

224 ms

jeffreybarr.com screenshot

About Website

Click here to check amazing Jeffrey Barr content. Otherwise, check out these important facts you probably never knew about jeffreybarr.com

Jeffrey Barr Resume

Visit jeffreybarr.com

Key Findings

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

Performance Metrics

jeffreybarr.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.2 s

100/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

jeffreybarr.com

120 ms

thesis

75 ms

17 ms

rice1011.css

76 ms

show_ads.js

12 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 14% of them (5 requests) were addressed to the original Jeffreybarr.com, 14% (5 requests) were made to Pagead2.googlesyndication.com and 11% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (296 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 49.1 kB (51%)

Content Size

95.9 kB

After Optimization

46.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jeffreybarr.com main page is 95.9 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. 35% of websites need less resources to load. Javascripts take 47.7 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 6.2 kB

  • Original 9.6 kB
  • After minification 9.3 kB
  • After compression 3.4 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 6.2 kB or 65% of the original size.

Image Optimization

-14%

Potential reduce by 1.4 kB

  • Original 9.9 kB
  • After minification 8.5 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. Obviously, Jeffrey Barr needs image optimization as it can save up to 1.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-36%

Potential reduce by 17.4 kB

  • Original 47.7 kB
  • After minification 45.8 kB
  • After compression 30.4 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 17.4 kB or 36% of the original size.

CSS Optimization

-84%

Potential reduce by 24.1 kB

  • Original 28.8 kB
  • After minification 25.7 kB
  • After compression 4.6 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. Jeffreybarr.com needs all CSS files to be minified and compressed as it can save up to 24.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (30%)

Requests Now

30

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jeffreybarr.com

jeffreybarr.com

120 ms

thesis

thesis

75 ms

17 ms

rice1011.css

rice1011.css

76 ms

show_ads.js

show_ads.js

12 ms

counter.js

counter.js

17 ms

urchin.js

urchin.js

6 ms

counter.asp

counter.asp

6 ms

ca-pub-3966187821299406.js

ca-pub-3966187821299406.js

58 ms

zrt_lookup.html

zrt_lookup.html

50 ms

show_ads_impl.js

show_ads_impl.js

60 ms

meter.asp

meter.asp

33 ms

analytics.js

analytics.js

204 ms

mpp.vindicosuite.com

mpp.vindicosuite.com

50 ms

__utm.gif

__utm.gif

23 ms

ricebk.jpg

ricebk.jpg

31 ms

meter.asp

meter.asp

23 ms

0

0

80 ms

ads

ads

224 ms

osd.js

osd.js

18 ms

ads

ads

296 ms

31 ms

blank.gif

blank.gif

56 ms

activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-208381787

activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-208381787

19 ms

activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-208381787

activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-208381787

17 ms

activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-208381787

activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-208381787

13 ms

activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-208381787

activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-208381787

18 ms

0

0

9 ms

m_js_controller.js

m_js_controller.js

22 ms

abg.js

abg.js

37 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

83 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

65 ms

s

s

48 ms

x_button_blue2.png

x_button_blue2.png

51 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

25 ms

Accessibility Review

jeffreybarr.com accessibility score

88

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

SEO Factors

jeffreybarr.com SEO score

58

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

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jeffreybarr.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 Jeffreybarr.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

jeffreybarr.com

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