5.2 sec in total
182 ms
4.7 sec
346 ms
Welcome to grecobe.com homepage info - get ready to check GRECOBE best content for India right away, or after learning these important things about grecobe.com
Visit grecobe.comWe analyzed Grecobe.com page load time and found that the first response time was 182 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 75% of websites can load faster.
grecobe.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value20.9 s
0/100
25%
Value16.8 s
0/100
10%
Value4,290 ms
1/100
30%
Value0.002
100/100
15%
Value37.7 s
0/100
10%
182 ms
1310 ms
54 ms
100 ms
241 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Grecobe.com, 79% (73 requests) were made to Cheresohealth.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Cheresohealth.com.
Page size can be reduced by 463.0 kB (21%)
2.3 MB
1.8 MB
In fact, the total size of Grecobe.com main page is 2.3 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. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 169.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. 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 169.2 kB or 84% of the original size.
Potential reduce by 152.6 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. Obviously, GRECOBE needs image optimization as it can save up to 152.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 49.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. This website has mostly compressed JavaScripts.
Potential reduce by 91.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. Grecobe.com needs all CSS files to be minified and compressed as it can save up to 91.8 kB or 48% of the original size.
Number of requests can be reduced by 55 (65%)
84
29
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GRECOBE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
grecobe.com
182 ms
1310 ms
js
54 ms
gtm.js
100 ms
style.min.css
241 ms
wc-blocks-vendors-style.css
182 ms
wc-blocks-style.css
249 ms
frontend.css
246 ms
badges.css
183 ms
owl.carousel.min.css
36 ms
owl.theme.default.css
72 ms
photoswipe.min.css
356 ms
default-skin.min.css
366 ms
woocommerce-layout.css
411 ms
twenty-twenty.css
416 ms
xoo-wsc-fonts.css
418 ms
xoo-wsc-style.css
420 ms
style.css
596 ms
elementor-fix.css
543 ms
style.css
643 ms
frontend.css
592 ms
jquery.min.js
652 ms
jquery-migrate.min.js
599 ms
analytics-talk-content-tracking.js
726 ms
gtm4wp-woocommerce-classic.js
767 ms
gtm4wp-woocommerce-enhanced.js
772 ms
index.js
774 ms
hooks.min.js
818 ms
wpm-public.p1.min.js
826 ms
js
50 ms
frontend.js
809 ms
colcade.js
810 ms
owl.carousel.min.js
20 ms
jquery.blockUI.min.js
810 ms
add-to-cart.min.js
810 ms
jquery.zoom.min.js
884 ms
jquery.flexslider.min.js
926 ms
photoswipe.min.js
1033 ms
photoswipe-ui-default.min.js
973 ms
single-product.min.js
972 ms
js.cookie.min.js
971 ms
woocommerce.min.js
1057 ms
cart-fragments.min.js
1122 ms
gtm4wp-contact-form-7-tracker.js
1424 ms
gtm4wp-form-move-tracker.js
1149 ms
api.js
36 ms
comment-reply.min.js
1149 ms
index.js
1204 ms
xoo-wsc-main.js
1206 ms
underscore.min.js
1283 ms
wp-util.min.js
1203 ms
add-to-cart-variation.min.js
1199 ms
fbevents.js
149 ms
gtm.js
1045 ms
bbf016e3842ddb77633c95a6ba484730
166 ms
img-1-1.jpg
958 ms
011-1-600x600.jpg
1043 ms
012-600x600.jpg
1112 ms
033-600x600.jpg
1169 ms
044-600x600.jpg
1235 ms
055-600x600.jpg
1282 ms
2eb4a691-007b-49af-9f61-04977f3742e6-768x768-1.jpg
1362 ms
unnamed-500x500-1.jpg
1331 ms
033-450x450.jpg
1406 ms
011-1-450x450.jpg
1463 ms
055-450x450.jpg
1523 ms
img-1-1-450x450.jpg
1515 ms
pro-4-450x450.jpg
1563 ms
prosman-450x450.jpg
1593 ms
Furosap-30-450x450.jpg
1564 ms
8AD3jaY2BkYGDgAWIxIGZiYARCESBmAfMYAAR6AEMAAAABAAAAANXtRbgAAAAA2AhRFAAAAADYCNuG
1 ms
star.woff
1528 ms
logo.png
1809 ms
init.js
145 ms
Woo-Side-Cart.woff
1570 ms
bundle.js
31 ms
recaptcha__en.js
231 ms
cheresohealth.com
1154 ms
img-1-1-100x100.jpg
854 ms
011-1-100x100.jpg
938 ms
012-100x100.jpg
960 ms
033-100x100.jpg
1056 ms
044-100x100.jpg
1071 ms
055-100x100.jpg
1172 ms
WooCommerce.woff
1194 ms
woocommerce-smallscreen.css
63 ms
print.css
176 ms
fallback
47 ms
fallback__ltr.css
3 ms
css
34 ms
logo_48.png
5 ms
font
20 ms
grecobe.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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.
grecobe.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
grecobe.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Grecobe.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 Grecobe.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.
grecobe.com
Open Graph description is not detected on the main page of GRECOBE. 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: