Tools & Wizards About Us
thepourreport.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

thepourreport.com

The Pour Report - Homebrewing, craft beer, & culinary musings from Brooklyn, New York

Page Load Speed

3.8 sec in total

First Response

440 ms

Resources Loaded

2.6 sec

Page Rendered

721 ms

thepourreport.com screenshot

About Website

Click here to check amazing The Pour Report content. Otherwise, check out these important facts you probably never knew about thepourreport.com

Discussing craft beer from a homebrewer's perspective including reviews, recipes, events, and travel. Live from Brooklyn, NYC, New York. Awarding winning homebrew Nick Ladd reporting.

Visit thepourreport.com

Key Findings

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

Performance Metrics

thepourreport.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

www.thepourreport.com

440 ms

ga.js

12 ms

style.css

95 ms

widget.css

64 ms

sociable.css

65 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 38% of them (28 requests) were addressed to the original Thepourreport.com, 14% (10 requests) were made to Apis.google.com and 14% (10 requests) were made to Stumbleupon.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 247.2 kB (41%)

Content Size

604.9 kB

After Optimization

357.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 115.7 kB

  • Original 138.7 kB
  • After minification 136.3 kB
  • After compression 23.0 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 115.7 kB or 83% of the original size.

Image Optimization

-17%

Potential reduce by 20.3 kB

  • Original 116.6 kB
  • After minification 96.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. Obviously, The Pour Report needs image optimization as it can save up to 20.3 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-26%

Potential reduce by 79.8 kB

  • Original 309.4 kB
  • After minification 308.5 kB
  • After compression 229.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 79.8 kB or 26% of the original size.

CSS Optimization

-78%

Potential reduce by 31.4 kB

  • Original 40.2 kB
  • After minification 30.2 kB
  • After compression 8.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. Thepourreport.com needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (51%)

Requests Now

57

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.thepourreport.com

www.thepourreport.com

440 ms

ga.js

ga.js

12 ms

style.css

style.css

95 ms

widget.css

widget.css

64 ms

sociable.css

sociable.css

65 ms

tablepress-combined.min.css

tablepress-combined.min.css

65 ms

jquery.js

jquery.js

160 ms

jquery-migrate.min.js

jquery-migrate.min.js

127 ms

sociable.js

sociable.js

127 ms

vuible.js

vuible.js

128 ms

addtofavorites.js

addtofavorites.js

129 ms

plusone.js

plusone.js

21 ms

__utm.gif

__utm.gif

13 ms

widgets.js

widgets.js

7 ms

hostedbadge.php

hostedbadge.php

11 ms

hostedbadge.php

hostedbadge.php

22 ms

hostedbadge.php

hostedbadge.php

2 ms

hostedbadge.php

hostedbadge.php

10 ms

hostedbadge.php

hostedbadge.php

2 ms

hostedbadge.php

hostedbadge.php

4 ms

hostedbadge.php

hostedbadge.php

2 ms

hostedbadge.php

hostedbadge.php

51 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

34 ms

hostedbadge.php

hostedbadge.php

3 ms

hostedbadge.php

hostedbadge.php

7 ms

related.css

related.css

101 ms

wp-embed.min.js

wp-embed.min.js

105 ms

plusone.js

plusone.js

147 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

162 ms

thepourreport.png

thepourreport.png

120 ms

rss.png

rss.png

119 ms

goog.png

goog.png

120 ms

insta.png

insta.png

119 ms

twitter.png

twitter.png

119 ms

fb.png

fb.png

154 ms

comment-bubble.png

comment-bubble.png

183 ms

LL_TPR_announce-400x348.jpg

LL_TPR_announce-400x348.jpg

185 ms

more.png

more.png

183 ms

closelabel.png

closelabel.png

183 ms

DSC3551-231x400.jpg

DSC3551-231x400.jpg

186 ms

IMG_3715-400x341.jpg

IMG_3715-400x341.jpg

207 ms

DSC3539-282x400.jpg

DSC3539-282x400.jpg

217 ms

DSC3536-268x400.jpg

DSC3536-268x400.jpg

219 ms

search.png

search.png

221 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

113 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

46 ms

fastbutton

fastbutton

37 ms

fastbutton

fastbutton

36 ms

fastbutton

fastbutton

32 ms

fastbutton

fastbutton

42 ms

like.php

like.php

175 ms

like.php

like.php

265 ms

like.php

like.php

332 ms

like.php

like.php

293 ms

like.php

like.php

293 ms

postmessageRelay

postmessageRelay

126 ms

settings

settings

202 ms

buttons.js

buttons.js

71 ms

developers.google.com

developers.google.com

419 ms

developers.google.com

developers.google.com

1289 ms

developers.google.com

developers.google.com

1538 ms

developers.google.com

developers.google.com

905 ms

developers.google.com

developers.google.com

678 ms

2254111616-postmessagerelay.js

2254111616-postmessagerelay.js

26 ms

rpc:shindig_random.js

rpc:shindig_random.js

9 ms

RJGwWDFd2_8.js

RJGwWDFd2_8.js

31 ms

FEppCFCt76d.png

FEppCFCt76d.png

30 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

7 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

embeds

embeds

51 ms

embeds

embeds

94 ms

embeds

embeds

135 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

22 ms

Accessibility Review

thepourreport.com accessibility score

89

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.

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

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

thepourreport.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

thepourreport.com SEO score

88

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

thepourreport.com

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