Tools & Wizards About Us
pulppours.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

pulppours.com

Fruit smoothies made fresh at your event - Pulp Pours

Page Load Speed

3 sec in total

First Response

71 ms

Resources Loaded

2.6 sec

Page Rendered

303 ms

pulppours.com screenshot

About Website

Visit pulppours.com now to see the best up-to-date Pulp Pours content and also check out these interesting facts you probably never knew about pulppours.com

Pulp Pours brings twenty years of experience making smoothies and fresh juices. We can design stations for massive functions, or we can wheel in our cool smoothie cart for a small party.

Visit pulppours.com

Key Findings

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

Performance Metrics

pulppours.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.171

70/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

pulppours.com

71 ms

pulppours.com

333 ms

flexnav.css

17 ms

owl.carousel.css

20 ms

jquery.fancybox.css

35 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 90% of them (60 requests) were addressed to the original Pulppours.com, 6% (4 requests) were made to Use.fontawesome.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Pulppours.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.9 kB (6%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pulppours.com main page is 1.8 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. 60% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 14.9 kB

  • Original 19.6 kB
  • After minification 16.3 kB
  • After compression 4.8 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 3.3 kB, which is 17% 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 14.9 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 24.3 kB

  • Original 1.6 MB
  • After minification 1.6 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. Pulp Pours images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 72.6 kB

  • Original 161.2 kB
  • After minification 161.2 kB
  • After compression 88.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 72.6 kB or 45% of the original size.

CSS Optimization

-13%

Potential reduce by 2.2 kB

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 15.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. Pulppours.com needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (39%)

Requests Now

61

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pulp Pours. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pulppours.com

pulppours.com

71 ms

pulppours.com

pulppours.com

333 ms

flexnav.css

flexnav.css

17 ms

owl.carousel.css

owl.carousel.css

20 ms

jquery.fancybox.css

jquery.fancybox.css

35 ms

master.css

master.css

48 ms

60b753d968.js

60b753d968.js

165 ms

modernizr.custom.js

modernizr.custom.js

215 ms

email-decode.min.js

email-decode.min.js

29 ms

jquery.min.js

jquery.min.js

349 ms

adtrak.cookies.min.js

adtrak.cookies.min.js

230 ms

ajax-form.js

ajax-form.js

360 ms

jquery.flexnav.min.js

jquery.flexnav.min.js

348 ms

picturefill.min.js

picturefill.min.js

347 ms

owl.carousel.js

owl.carousel.js

468 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

442 ms

carousels.js

carousels.js

489 ms

run.js

run.js

508 ms

analytics.js

analytics.js

18 ms

microsoft.svg

microsoft.svg

139 ms

amazon.svg

amazon.svg

142 ms

spotify.svg

spotify.svg

142 ms

uber.svg

uber.svg

143 ms

instagram.svg

instagram.svg

143 ms

logo.jpg

logo.jpg

142 ms

menu.svg

menu.svg

144 ms

instagram.svg

instagram.svg

142 ms

linkedin.svg

linkedin.svg

144 ms

facebook.svg

facebook.svg

145 ms

email.svg

email.svg

147 ms

phone.svg

phone.svg

147 ms

strawberry-home.png

strawberry-home.png

148 ms

strawberry-home-on.png

strawberry-home-on.png

154 ms

intro-bg.png

intro-bg.png

156 ms

index.png

index.png

172 ms

tick.svg

tick.svg

166 ms

button-bg.png

button-bg.png

178 ms

strawberries.png

strawberries.png

188 ms

banana.png

banana.png

193 ms

01.jpg

01.jpg

201 ms

02.jpg

02.jpg

202 ms

03.jpg

03.jpg

475 ms

04.jpg

04.jpg

214 ms

05.jpg

05.jpg

240 ms

06.jpg

06.jpg

240 ms

ebay.svg

ebay.svg

242 ms

60b753d968.css

60b753d968.css

133 ms

07.jpg

07.jpg

242 ms

collect

collect

37 ms

08.jpg

08.jpg

131 ms

testimonial-bg.png

testimonial-bg.png

133 ms

index2.png

index2.png

128 ms

prev.png

prev.png

129 ms

font-awesome-css.min.css

font-awesome-css.min.css

13 ms

next.png

next.png

142 ms

pear-mirror.png

pear-mirror.png

140 ms

index3.jpg

index3.jpg

134 ms

footer-bg.jpg

footer-bg.jpg

474 ms

footer-fruit.png

footer-fruit.png

180 ms

sourcesanspro-regular-webfont.svg

sourcesanspro-regular-webfont.svg

482 ms

sourcesanspro-regular-webfont.woff

sourcesanspro-regular-webfont.woff

452 ms

litterbox-icg-regular-webfont.svg

litterbox-icg-regular-webfont.svg

584 ms

litterbox-icg-regular-webfont.woff

litterbox-icg-regular-webfont.woff

468 ms

sourcesanspro-it-webfont.svg

sourcesanspro-it-webfont.svg

653 ms

sourcesanspro-it-webfont.woff

sourcesanspro-it-webfont.woff

1803 ms

js

js

68 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

10 ms

Accessibility Review

pulppours.com accessibility score

73

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

Image elements do not have [alt] attributes

High

<object> elements do not have alternate text

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pulppours.com SEO score

84

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

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

pulppours.com

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