5.2 sec in total
116 ms
4.3 sec
830 ms
Welcome to thegrandriver.com homepage info - get ready to check Thegrandriver best content for United States right away, or after learning these important things about thegrandriver.com
Perficient Digital is a creative digital agency with deep roots in technology and execution. We pair beautiful customer experiences with great implementation.
Visit thegrandriver.comWe analyzed Thegrandriver.com page load time and found that the first response time was 116 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
thegrandriver.com performance score
116 ms
1008 ms
22 ms
71 ms
58 ms
Our browser made a total of 172 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Thegrandriver.com, 47% (80 requests) were made to Maps.googleapis.com and 38% (66 requests) were made to Commerce.perficient.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Pi.pardot.com.
Page size can be reduced by 1.2 MB (23%)
5.0 MB
3.8 MB
In fact, the total size of Thegrandriver.com main page is 5.0 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. 70% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 174.3 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 24.0 kB, which is 13% 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 174.3 kB or 91% of the original size.
Potential reduce by 130.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. Thegrandriver images are well optimized though.
Potential reduce by 707.0 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 707.0 kB or 68% of the original size.
Potential reduce by 150.2 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. Thegrandriver.com needs all CSS files to be minified and compressed as it can save up to 150.2 kB or 82% of the original size.
Number of requests can be reduced by 60 (38%)
160
100
The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thegrandriver. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
thegrandriver.com
116 ms
commerce.perficient.com
1008 ms
css
22 ms
js
71 ms
ccm.base.css
58 ms
jquery.js
186 ms
ccm.base.js
62 ms
skrollr.min.js
66 ms
jquery.bxslider.js
126 ms
jquery.scrollstop.js
88 ms
jquery.easing.min.js
93 ms
jquery.mousewheel.js
97 ms
jquery.bxslider.css
117 ms
framer.fluid.min.css
117 ms
framer.fluid.responsive.min.css
124 ms
jquery.fancybox.css
129 ms
gri2014.min.css
258 ms
gri2014.responsive.min.css
199 ms
fonts.css
155 ms
bootstrap.js
156 ms
gri.js
160 ms
gri2014.min.js
245 ms
gri2014.responsive.min.js
201 ms
jquery.easytabs.min.js
202 ms
jquery.validate.min.js
212 ms
jquery.unveil.min.js
217 ms
2129281749.js
311 ms
pdc-type.png
63 ms
menu_icon.jpg
62 ms
nav_logo.png
65 ms
partners_banner-magento.png
66 ms
partners_banner-magento-2x.png
67 ms
partners_banner-insite.png
63 ms
partners_banner-insite-2x.png
69 ms
partners_banner-ibm.png
181 ms
partners_banner-ibm-2x.png
179 ms
home-_featured_lcc.jpg
186 ms
reiman-bridge-x2.png
182 ms
burton-tower-x2.png
181 ms
gateway-arch-x2.png
183 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
60 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
66 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
66 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
65 ms
gtm.js
64 ms
vision_bg.jpg
163 ms
vision_wheel_big.png
196 ms
vision_wheel.png
167 ms
vision_board.png
220 ms
vision_text1.png
164 ms
vision_text2.png
165 ms
vision_ipad.png
168 ms
create_bg.jpg
165 ms
create_flower4.png
197 ms
create_floral_embellishment.png
280 ms
create_flower2.png
238 ms
create_flower1.png
218 ms
create_vases.png
219 ms
create_ipad.png
602 ms
solution_bg.jpg
282 ms
solution_phones.png
408 ms
solution_orange.png
289 ms
solution_pear.png
277 ms
solution_cherry.png
317 ms
results_bg.jpg
311 ms
results_glass.png
359 ms
results_glass2.png
372 ms
results_computer_wine_2.png
410 ms
fancybox_sprite.png
331 ms
simple-background-x2.png
423 ms
reiman-bridge-bubble-x2.png
369 ms
burton-tower-bubble-x2.png
373 ms
gateway-arch-bubble-x2.png
400 ms
social-icons.png
401 ms
gk5FxslNkTTHtojXrkp-xONSK5BxN3NFS4EJkViHIqo.woff
110 ms
gk5FxslNkTTHtojXrkp-xF1YPouZEKgzpqZW9wN-3Ek.woff
111 ms
8751.js
63 ms
analytics.js
23 ms
collect
12 ms
common.js
19 ms
map.js
35 ms
util.js
87 ms
marker.js
84 ms
geocoder.js
82 ms
geometry.js
82 ms
directions.js
83 ms
pd.js
11 ms
analytics
2236 ms
onion.js
40 ms
openhand_8_8.cur
112 ms
ViewportInfoService.GetViewportInfo
146 ms
stats.js
62 ms
controls.js
76 ms
ViewportInfoService.GetViewportInfo
179 ms
ViewportInfoService.GetViewportInfo
177 ms
infowindow.js
48 ms
css
151 ms
custom-marker.png
107 ms
transparent.png
83 ms
google4.png
102 ms
mapcnt6.png
156 ms
sv5.png
162 ms
google_white5.png
98 ms
vt
136 ms
vt
161 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
107 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
119 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
144 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
163 ms
vt
93 ms
vt
91 ms
vt
162 ms
vt
138 ms
vt
160 ms
vt
143 ms
vt
160 ms
vt
196 ms
vt
189 ms
vt
212 ms
vt
188 ms
vt
191 ms
vt
190 ms
vt
246 ms
vt
200 ms
vt
261 ms
vt
208 ms
vt
213 ms
vt
239 ms
vt
313 ms
vt
281 ms
vt
265 ms
vt
279 ms
vt
282 ms
vt
278 ms
vt
277 ms
vt
309 ms
vt
318 ms
vt
300 ms
vt
296 ms
vt
337 ms
vt
360 ms
vt
324 ms
vt
318 ms
vt
342 ms
vt
353 ms
vt
279 ms
vt
263 ms
vt
289 ms
vt
274 ms
vt
284 ms
vt
306 ms
vt
316 ms
vt
281 ms
vt
295 ms
vt
302 ms
vt
335 ms
vt
312 ms
vt
342 ms
vt
308 ms
vt
356 ms
vt
336 ms
vt
340 ms
vt
319 ms
vt
256 ms
vt
284 ms
vt
275 ms
vt
279 ms
vt
285 ms
vt
289 ms
AuthenticationService.Authenticate
299 ms
vt
301 ms
vt
308 ms
thegrandriver.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thegrandriver.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 Thegrandriver.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.
thegrandriver.com
Open Graph description is not detected on the main page of Thegrandriver. 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: