Tools & Wizards About Us
goingbonkers.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

goingbonkers.com

Bonkers Family Fun Center | Birthday Parties, Arcade & Play Maze

Page Load Speed

1.1 sec in total

First Response

8 ms

Resources Loaded

988 ms

Page Rendered

85 ms

goingbonkers.com screenshot

About Website

Welcome to goingbonkers.com homepage info - get ready to check Going Bonkers best content for United States right away, or after learning these important things about goingbonkers.com

Find your way through our Play Maze, play and win in our Arcade, book a party, and taste our homemade pizza at Bonkers!

Visit goingbonkers.com

Key Findings

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

goingbonkers.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value590 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.196

63/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

goingbonkers.com

8 ms

www.goingbonkers.com

323 ms

e363a6b9027056c7827b0b909bff5d6f.min.css

125 ms

jquery.min.js

23 ms

jquery-migrate.min.js

16 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 90% of them (74 requests) were addressed to the original Goingbonkers.com, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (323 ms) belongs to the original domain Goingbonkers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.2 kB (8%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 56.5 kB

  • Original 70.9 kB
  • After minification 69.2 kB
  • After compression 14.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 56.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 595.1 kB
  • After minification 595.1 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. Going Bonkers images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 32.7 kB

  • Original 213.1 kB
  • After minification 213.1 kB
  • After compression 180.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.7 kB or 15% of the original size.

CSS Optimization

-1%

Potential reduce by 2.0 kB

  • Original 273.5 kB
  • After minification 273.5 kB
  • After compression 271.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. Goingbonkers.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (81%)

Requests Now

79

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

goingbonkers.com

goingbonkers.com

8 ms

www.goingbonkers.com

www.goingbonkers.com

323 ms

e363a6b9027056c7827b0b909bff5d6f.min.css

e363a6b9027056c7827b0b909bff5d6f.min.css

125 ms

jquery.min.js

jquery.min.js

23 ms

jquery-migrate.min.js

jquery-migrate.min.js

16 ms

all.css

all.css

41 ms

style.min.css

style.min.css

26 ms

cssua.js

cssua.js

21 ms

fusion-animations.js

fusion-animations.js

18 ms

fusion-vertical-menu-widget.js

fusion-vertical-menu-widget.js

17 ms

modernizr.js

modernizr.js

22 ms

fusion.js

fusion.js

23 ms

isotope.js

isotope.js

26 ms

packery.js

packery.js

24 ms

bootstrap.transition.js

bootstrap.transition.js

27 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

29 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

27 ms

jquery.easing.js

jquery.easing.js

29 ms

jquery.fitvids.js

jquery.fitvids.js

33 ms

jquery.flexslider.js

jquery.flexslider.js

30 ms

jquery.ilightbox.js

jquery.ilightbox.js

57 ms

jquery.mousewheel.js

jquery.mousewheel.js

30 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

30 ms

jquery.fade.js

jquery.fade.js

31 ms

imagesLoaded.js

imagesLoaded.js

33 ms

fusion-equal-heights.js

fusion-equal-heights.js

34 ms

fusion-parallax.js

fusion-parallax.js

35 ms

fusion-video-general.js

fusion-video-general.js

35 ms

fusion-video-bg.js

fusion-video-bg.js

37 ms

fusion-lightbox.js

fusion-lightbox.js

38 ms

fusion-tooltip.js

fusion-tooltip.js

37 ms

fusion-sharing-box.js

fusion-sharing-box.js

40 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

39 ms

fusion-youtube.js

fusion-youtube.js

40 ms

vimeoPlayer.js

vimeoPlayer.js

42 ms

avada-general-footer.js

avada-general-footer.js

40 ms

avada-quantity.js

avada-quantity.js

41 ms

avada-crossfade-images.js

avada-crossfade-images.js

43 ms

avada-select.js

avada-select.js

41 ms

avada-tabs-widget.js

avada-tabs-widget.js

33 ms

jquery.elasticslider.js

jquery.elasticslider.js

32 ms

avada-events.js

avada-events.js

31 ms

fusion-alert.js

fusion-alert.js

29 ms

awb-off-canvas.js

awb-off-canvas.js

28 ms

fusion-flexslider.js

fusion-flexslider.js

29 ms

fusion-column-legacy.js

fusion-column-legacy.js

29 ms

jquery.textillate.js

jquery.textillate.js

28 ms

fusion-title.js

fusion-title.js

28 ms

fusion-button.js

fusion-button.js

25 ms

fusion-gallery.js

fusion-gallery.js

26 ms

fusion-container.js

fusion-container.js

29 ms

avada-elastic-slider.js

avada-elastic-slider.js

26 ms

avada-gravity-forms.js

avada-gravity-forms.js

28 ms

avada-drop-down.js

avada-drop-down.js

28 ms

avada-to-top.js

avada-to-top.js

29 ms

avada-header.js

avada-header.js

28 ms

avada-menu.js

avada-menu.js

27 ms

avada-sidebars.js

avada-sidebars.js

28 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

26 ms

avada-scrollspy.js

avada-scrollspy.js

27 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

25 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

27 ms

fusion-general-global.js

fusion-general-global.js

26 ms

fusion-video.js

fusion-video.js

23 ms

fusion-column.js

fusion-column.js

24 ms

gtm.js

gtm.js

176 ms

883bec3cc16a688911c55992f.js

883bec3cc16a688911c55992f.js

230 ms

app.js

app.js

200 ms

feg-logo-w160px.png

feg-logo-w160px.png

109 ms

bonkers-logo-2.png

bonkers-logo-2.png

146 ms

bonkers-topeka.jpg

bonkers-topeka.jpg

172 ms

location-card-kids-playing-1.jpg

location-card-kids-playing-1.jpg

145 ms

location-card-kids-climbing.jpg

location-card-kids-climbing.jpg

148 ms

location-card-kids-sliding.jpg

location-card-kids-sliding.jpg

148 ms

location-card-teens-1.jpg

location-card-teens-1.jpg

148 ms

location-card-teens-2.jpg

location-card-teens-2.jpg

173 ms

awb-icons.woff

awb-icons.woff

77 ms

js

js

52 ms

analytics.js

analytics.js

15 ms

collect

collect

14 ms

collect

collect

94 ms

bonkers-logo.png

bonkers-logo.png

13 ms

Accessibility Review

goingbonkers.com accessibility score

98

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.

Best Practices

goingbonkers.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

goingbonkers.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 Goingbonkers.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 Goingbonkers.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

goingbonkers.com

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