1.6 sec in total
63 ms
1.3 sec
196 ms
Visit grandave.com now to see the best up-to-date Grand Ave content for United States and also check out these interesting facts you probably never knew about grandave.com
Visit grandave.comWe analyzed Grandave.com page load time and found that the first response time was 63 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
grandave.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value6.3 s
10/100
25%
Value5.8 s
49/100
10%
Value190 ms
90/100
30%
Value0.016
100/100
15%
Value6.4 s
60/100
10%
63 ms
873 ms
21 ms
21 ms
23 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 68% of them (39 requests) were addressed to the original Grandave.com, 12% (7 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (873 ms) belongs to the original domain Grandave.com.
Page size can be reduced by 441.9 kB (53%)
836.3 kB
394.4 kB
In fact, the total size of Grandave.com main page is 836.3 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. 50% of websites need less resources to load. Javascripts take 369.4 kB which makes up the majority of the site volume.
Potential reduce by 34.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. This page needs HTML code to be minified as it can gain 4.7 kB, which is 11% 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 34.4 kB or 82% of the original size.
Potential reduce by 5.9 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. Grand Ave images are well optimized though.
Potential reduce by 258.8 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 258.8 kB or 70% of the original size.
Potential reduce by 142.8 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. Grandave.com needs all CSS files to be minified and compressed as it can save up to 142.8 kB or 82% of the original size.
Number of requests can be reduced by 34 (77%)
44
10
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grand Ave. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
grandave.com
63 ms
www.grandave.com
873 ms
system.base.css
21 ms
shadowbox.css
21 ms
date.css
23 ms
field.css
22 ms
google_cse.css
22 ms
logintoboggan.css
23 ms
simpleads.css
23 ms
uc_order.css
24 ms
uc_product.css
24 ms
uc_store.css
24 ms
calendar_multiday.css
33 ms
views.css
35 ms
ctools.css
34 ms
panels.css
34 ms
print_ui.theme.css
34 ms
bootstrap.min.css
20 ms
overrides.css
33 ms
style.css
35 ms
vertical-tabs.css
33 ms
jquery.min.js
38 ms
jquery.once.js
35 ms
drupal.js
36 ms
shadowbox.js
38 ms
shadowbox_auto.js
35 ms
bootstrap.min.js
24 ms
contentanalysis.js
36 ms
contentoptimizer.js
38 ms
google_cse.js
38 ms
simpleads.js
38 ms
googleanalytics.js
38 ms
grandave_2015.js
38 ms
0fee7021873b74c3c0f67e63d38ca1869a993f09.js
35 ms
bootstrap.js
66 ms
css
72 ms
analytics.js
127 ms
logo.png
126 ms
Live.jpg
37 ms
Dine.jpg
38 ms
Shop.jpg
32 ms
ls.jpg
30 ms
9c4onn5Bi.jpeg
29 ms
KW_OddCouple_Final_0.jpg
37 ms
UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf
67 ms
-_Ctzj9b56b8RgXW8FAricDdSZkkecOE1hvV7ZHvhyU.ttf
72 ms
xkvoNo9fC8O2RDydKj12b8DdSZkkecOE1hvV7ZHvhyU.ttf
89 ms
JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf
93 ms
glyphicons-halflings-regular.woff
20 ms
css
77 ms
collect
29 ms
collect
62 ms
wAAABAAAAAAABAAAAQAAAAAAAAAAAAAAAAAAAAcAAAAAAAAAAAAAAAACAAAABAAAOAQAAAAEAAAAAAAAAAAKABQAHgBmAKYA5gABAAAABwAuAAIAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADgAAAAEAAAAAAAIADgBHAAEAAAAAAAMADgAkAAEAAAAAAAQADgBVAAEAAAAAAAUAFgAOAAEAAAAAAAYABwAyAAEAAAAAAAoANABjAAMAAQQJAAEADgAAAAMAAQQJAAIADgBHAAMAAQQJAAMADgAkAAMAAQQJAAQADgBVAAMAAQQJAAUAFgAOAAMAAQQJAAYADgA5AAMAAQQJAAoANABjAGkAYwBvAG0AbwBvAG4AVgBlAHIAcwBpAG8AbgAgADEALgAwAGkAYwBvAG0AbwBvAG5pY29tb29uAGkAYwBvAG0AbwBvAG4AUgBlAGcAdQBsAGEAcgBpAGMAbwBtAG8AbwBuAEYAbwBuAHQAIABnAGUAbgBlAHIAYQB0AGUAZAAgAGIAeQAgAEkAYwBvAE0AbwBvAG4ALgAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
5 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
13 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
12 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
12 ms
ga-audiences
36 ms
grandave.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
grandave.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
grandave.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grandave.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 Grandave.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.
grandave.com
Open Graph description is not detected on the main page of Grand Ave. 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: