3.3 sec in total
129 ms
2.4 sec
760 ms
Welcome to crispandgreen.com homepage info - get ready to check CRISP And GREEN best content for United States right away, or after learning these important things about crispandgreen.com
Fast, casual, healthy restaurant. Enjoy made-from-scratch salads, grain bowls & smoothies crafted with fresh ingredients daily.
Visit crispandgreen.comWe analyzed Crispandgreen.com page load time and found that the first response time was 129 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
crispandgreen.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value16.7 s
0/100
25%
Value10.4 s
8/100
10%
Value4,090 ms
1/100
30%
Value0.023
100/100
15%
Value21.2 s
1/100
10%
129 ms
118 ms
90 ms
24 ms
58 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 63% of them (69 requests) were addressed to the original Crispandgreen.com, 11% (12 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (800 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 94.3 kB (5%)
1.9 MB
1.9 MB
In fact, the total size of Crispandgreen.com main page is 1.9 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. 85% 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.1 MB which makes up the majority of the site volume.
Potential reduce by 58.6 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 58.6 kB or 77% of the original size.
Potential reduce by 1.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. CRISP And GREEN images are well optimized though.
Potential reduce by 13.1 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 21.1 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. Crispandgreen.com has all CSS files already compressed.
Number of requests can be reduced by 74 (79%)
94
20
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CRISP And GREEN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
crispandgreen.com
129 ms
crispandgreen.com
118 ms
js
90 ms
js_composer.min.css
24 ms
sbi-styles.min.css
58 ms
variables-skeleton.min.css
55 ms
variables-full.min.css
56 ms
rsvp-v1.min.css
56 ms
dashicons.min.css
53 ms
common-skeleton.min.css
63 ms
common-full.min.css
77 ms
tickets.min.css
87 ms
tribe-events-pro-mini-calendar-block.min.css
81 ms
animate.css
75 ms
jquery.bxslider.css
85 ms
prettyPhoto.css
81 ms
font-awesome.min.css
111 ms
css
78 ms
elegant-icons.css
116 ms
et-frontend.css
117 ms
et-responsive.css
139 ms
style.css
145 ms
ar.css
142 ms
locations.css
163 ms
wpex-the-events-calendar.css
162 ms
css2
113 ms
style.css
163 ms
wpex-mobile-menu-breakpoint-min.css
192 ms
wpex-wpbakery.css
189 ms
ticons.min.css
195 ms
vcex-shortcodes.css
201 ms
rsvp.min.css
193 ms
tpp.min.css
199 ms
jquery.min.js
225 ms
jquery-migrate.min.js
221 ms
frontend-gtag.min.js
221 ms
isotope.js
220 ms
jquery.bxslider.js
241 ms
imagesloaded.min.js
222 ms
jquery.prettyPhoto.js
241 ms
style.css
221 ms
rs6.css
208 ms
wow.js
201 ms
et-frontend.js
199 ms
rbtools.min.js
212 ms
rs6.min.js
205 ms
rsvp.min.js
204 ms
ticket-details.min.js
201 ms
main.js
187 ms
concat.js
187 ms
sidr.min.js
183 ms
hoverIntent.min.js
184 ms
supersubs.min.js
225 ms
superfish.min.js
157 ms
wpex-superfish.min.js
152 ms
jquery.easing.min.js
172 ms
total.min.js
170 ms
js_composer_front.min.js
166 ms
jquery.backstretch.min.js
149 ms
jquery.flexverticalcenter.js
194 ms
script.js
193 ms
js
368 ms
analytics.js
291 ms
gtm.js
297 ms
js
554 ms
js
493 ms
hotjar-654025.js
669 ms
sbi-sprite.png
227 ms
logo-r.png
227 ms
C_G_Stills-39.jpg
437 ms
P1455124_edit-4.jpg
486 ms
C_G_LYNC3.jpg
488 ms
CG_DownloadApp.png
226 ms
Loyalty_Phone-1.png
666 ms
icon-appstore-300x89.png
437 ms
icon-googleplay-300x89.png
429 ms
fbevents.js
433 ms
56ccAwpNmkI
653 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
447 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
561 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
589 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf
696 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
624 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
696 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
623 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
723 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
694 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
800 ms
insight.min.js
411 ms
ticons.woff
563 ms
collect
134 ms
collect
127 ms
collect
312 ms
375 ms
327 ms
www-player.css
105 ms
www-embed-player.js
203 ms
base.js
301 ms
modules.2472296d2d26f0040059.js
273 ms
wpex-mobile-menu-breakpoint-max.css
195 ms
ga-audiences
596 ms
439 ms
ad_status.js
210 ms
e4KNrNezHvGe_SA60BxYba8nt93XKTbVAQxfSxUqUHI.js
117 ms
embed.js
42 ms
39 ms
id
35 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
247 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
246 ms
Create
34 ms
crispandgreen.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.
crispandgreen.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
Browser errors were logged to the console
Page has valid source maps
crispandgreen.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Crispandgreen.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 Crispandgreen.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.
crispandgreen.com
Open Graph data is detected on the main page of CRISP And GREEN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: