Tools & Wizards About Us
jelly-ball.com screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

jelly-ball.com

Jelly Ball - The Drink Stop - Lynnhaven Mall, Virginia Beach, VA

Page Load Speed

1 sec in total

First Response

21 ms

Resources Loaded

904 ms

Page Rendered

98 ms

jelly-ball.com screenshot

About Website

Welcome to jelly-ball.com homepage info - get ready to check Jelly Ball best content right away, or after learning these important things about jelly-ball.com

Jelly Ball is your Drink Stop in Virginia Beach. Located in Lynnhaven Mall in Virginia Beach, VA for over a decade, Jelly Ball serves delicious smoothies, slushies, milkshakes and boba/pearl drinks al...

Visit jelly-ball.com

Key Findings

We analyzed Jelly-ball.com page load time and found that the first response time was 21 ms and then it took 1 sec 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

jelly-ball.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

jelly-ball.com

21 ms

www.jelly-ball.com

486 ms

css

22 ms

bootstrap.css

217 ms

creative.css

115 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 63% of them (12 requests) were addressed to the original Jelly-ball.com, 21% (4 requests) were made to Fonts.gstatic.com and 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (486 ms) belongs to the original domain Jelly-ball.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.8 kB (19%)

Content Size

154.1 kB

After Optimization

125.2 kB

  • HTML
  • Images

In fact, the total size of Jelly-ball.com main page is 154.1 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. 30% of websites need less resources to load. Images take 149.8 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 3.0 kB

  • Original 4.3 kB
  • After minification 3.6 kB
  • After compression 1.2 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 641 B, which is 15% 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 3.0 kB or 71% of the original size.

Image Optimization

-17%

Potential reduce by 25.8 kB

  • Original 149.8 kB
  • After minification 124.0 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, Jelly Ball needs image optimization as it can save up to 25.8 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 8 (62%)

Requests Now

13

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jelly-ball.com

jelly-ball.com

21 ms

www.jelly-ball.com

www.jelly-ball.com

486 ms

css

css

22 ms

bootstrap.css

bootstrap.css

217 ms

creative.css

creative.css

115 ms

styles.css

styles.css

105 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

5 ms

jquery.fittext.min.js

jquery.fittext.min.js

44 ms

loadr.js

loadr.js

167 ms

loadrImage.js

loadrImage.js

167 ms

bootstrap.js

bootstrap.js

106 ms

bundle.js

bundle.js

265 ms

jb-logo.svg

jb-logo.svg

208 ms

burst-bg.png

burst-bg.png

167 ms

pattern.png

pattern.png

88 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

11 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

14 ms

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMQg.ttf

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMQg.ttf

16 ms

mFT0WbgBwKPR_Z4hGN2qgx8D0A.ttf

mFT0WbgBwKPR_Z4hGN2qgx8D0A.ttf

18 ms

Accessibility Review

jelly-ball.com accessibility score

79

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jelly-ball.com best practices score

83

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

Page has valid source maps

SEO Factors

jelly-ball.com SEO score

100

Search Engine Optimization Advices

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

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 Jelly-ball.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 Jelly-ball.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

jelly-ball.com

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