Tools & Wizards About Us
pubfood.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pubfood.org

Open source header bidding framework built by publishers for publishers.

Page Load Speed

573 ms in total

First Response

24 ms

Resources Loaded

180 ms

Page Rendered

369 ms

pubfood.org screenshot

About Website

Visit pubfood.org now to see the best up-to-date Pubfood content for United States and also check out these interesting facts you probably never knew about pubfood.org

Visit pubfood.org

Key Findings

We analyzed Pubfood.org page load time and found that the first response time was 24 ms and then it took 549 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

pubfood.org performance score

0

Network Requests Diagram

pubfood.org

24 ms

bootstrap.min.css

12 ms

styles.css

27 ms

jquery.min.js

75 ms

bootstrap.min.js

24 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 90% of them (18 requests) were addressed to the original Pubfood.org, 5% (1 request) were made to Ajax.googleapis.com and 5% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (75 ms) relates to the external source Ajax.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.5 kB (32%)

Content Size

531.6 kB

After Optimization

364.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pubfood.org main page is 531.6 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. Images take 290.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 4.2 kB

  • Original 6.2 kB
  • After minification 5.3 kB
  • After compression 1.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 826 B, which is 13% 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 4.2 kB or 69% of the original size.

Image Optimization

-2%

Potential reduce by 6.2 kB

  • Original 290.9 kB
  • After minification 284.6 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. Pubfood images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 32.0 kB

  • Original 86.4 kB
  • After minification 86.4 kB
  • After compression 54.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 32.0 kB or 37% of the original size.

CSS Optimization

-84%

Potential reduce by 125.1 kB

  • Original 148.1 kB
  • After minification 142.0 kB
  • After compression 23.0 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. Pubfood.org needs all CSS files to be minified and compressed as it can save up to 125.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (16%)

Requests Now

19

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pubfood.org

pubfood.org

24 ms

bootstrap.min.css

bootstrap.min.css

12 ms

styles.css

styles.css

27 ms

jquery.min.js

jquery.min.js

75 ms

bootstrap.min.js

bootstrap.min.js

24 ms

scripts.js

scripts.js

36 ms

logo.png

logo.png

36 ms

half-circle-1.png

half-circle-1.png

37 ms

icon-maze.png

icon-maze.png

37 ms

icon-spring.png

icon-spring.png

40 ms

icon-lock.png

icon-lock.png

35 ms

half-circle-2.png

half-circle-2.png

39 ms

icon-fork-and-knife.png

icon-fork-and-knife.png

38 ms

logo-2.png

logo-2.png

38 ms

icon-twitter.png

icon-twitter.png

39 ms

bg-top-wrapper-outer.jpg

bg-top-wrapper-outer.jpg

11 ms

bg-section-home-1-outer.jpg

bg-section-home-1-outer.jpg

18 ms

li-arrow-3-1.png

li-arrow-3-1.png

9 ms

bg-section-home-2-outer.jpg

bg-section-home-2-outer.jpg

11 ms

analytics.js

analytics.js

39 ms

SEO Factors

pubfood.org SEO score

0

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 Pubfood.org 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 Pubfood.org 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

pubfood.org

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