2 sec in total
244 ms
1.2 sec
520 ms
Click here to check amazing Graceland Bounce content. Otherwise, check out these important facts you probably never knew about gracelandbounce.com
Bounce House Rentals Hinesville, GA: For the most fun inflatable rentals Graceland Bounce can't be beat for bounce house rentals in Hinesville, GA!
Visit gracelandbounce.comWe analyzed Gracelandbounce.com page load time and found that the first response time was 244 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
gracelandbounce.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value10.1 s
0/100
25%
Value6.7 s
36/100
10%
Value900 ms
31/100
30%
Value0.14
79/100
15%
Value17.8 s
4/100
10%
244 ms
218 ms
107 ms
107 ms
106 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 11% of them (10 requests) were addressed to the original Gracelandbounce.com, 58% (52 requests) were made to Files.sysers.com and 6% (5 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (277 ms) relates to the external source Kit.fontawesome.com.
Page size can be reduced by 167.3 kB (7%)
2.5 MB
2.3 MB
In fact, the total size of Gracelandbounce.com main page is 2.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 47.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 7.0 kB, which is 12% 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 47.2 kB or 80% of the original size.
Potential reduce by 84.5 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. Graceland Bounce images are well optimized though.
Potential reduce by 17.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. This website has mostly compressed JavaScripts.
Potential reduce by 17.9 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. Gracelandbounce.com needs all CSS files to be minified and compressed as it can save up to 17.9 kB or 47% of the original size.
Number of requests can be reduced by 35 (44%)
80
45
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Graceland Bounce. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
gracelandbounce.com
244 ms
js
218 ms
general_functions.js
107 ms
textarea_tab.js
107 ms
ajax_lib.js
106 ms
general.css
152 ms
ers2_default.css
149 ms
checklist_color.js
153 ms
tcal.js
197 ms
tcal.css
198 ms
basic_template.js
196 ms
bootstrap.min.css
177 ms
e22b920868.js
277 ms
ie10-viewport-bug-workaround.css
176 ms
css
176 ms
css
212 ms
css
233 ms
font-awesome.min.css
195 ms
flexslider.css
176 ms
owl.carousel.css
188 ms
animate.css
196 ms
styles.css
206 ms
swdrecentlyviewed.css
232 ms
pixel.js
210 ms
jquery.min.js
211 ms
bootstrap.min.js
230 ms
jquery-2.2.4.min.js
176 ms
ie10-viewport-bug-workaround.js
186 ms
jquery.flexslider-min.js
193 ms
owl.carousel.min.js
192 ms
wow.min.js
227 ms
main.js
227 ms
swdsc.js
263 ms
swdrecentlyviewed.js
238 ms
loader.js
207 ms
analytics.js
131 ms
header-logo.png
39 ms
icon-calendar.png
33 ms
icon-cart.png
33 ms
slider-1.jpg
193 ms
slider-2.jpg
120 ms
slider-3.jpg
120 ms
slider-4.jpg
125 ms
slider-5.jpg
127 ms
wel-1.jpg
192 ms
wel-2.jpg
125 ms
feature-1.jpg
193 ms
feature-2.jpg
193 ms
feature-3.jpg
193 ms
feature-4.jpg
193 ms
feature-5.jpg
196 ms
feature-6.jpg
199 ms
feature-7.jpg
196 ms
feature-8.jpg
197 ms
feature-9.jpg
195 ms
new-prod-1.jpg
195 ms
new-prod-2.jpg
225 ms
new-prod-4.jpg
224 ms
new-prod-5.jpg
224 ms
new-prod-6.jpg
223 ms
new-prod-8.jpg
223 ms
new-prod-9.jpg
223 ms
new-prod-10.jpg
226 ms
new-prod-11.jpg
227 ms
parallax-feature-1.jpg
228 ms
car-1.jpg
227 ms
car-2.jpg
223 ms
car-3.jpg
226 ms
car-4.jpg
228 ms
car-5.jpg
228 ms
car-6.jpg
228 ms
car-7.jpg
230 ms
sdk.js
188 ms
car-8.jpg
206 ms
logo.png
233 ms
header-bg.jpg
171 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
115 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
148 ms
glyphicons-halflings-regular.woff
81 ms
rP2Hp2yn6lkG50LoCZOIGA.ttf
172 ms
fontawesome-webfont.woff
83 ms
kmK-Zq45GAvOdnaW6y1C9y4.ttf
171 ms
parallax-1.jpg
169 ms
footer-bg.jpg
164 ms
collect
78 ms
sdk.js
68 ms
js
64 ms
98 ms
flexslider-icon.woff
11 ms
gracelandbounce.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
gracelandbounce.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
gracelandbounce.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gracelandbounce.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 Gracelandbounce.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.
gracelandbounce.com
Open Graph description is not detected on the main page of Graceland Bounce. 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: