8.1 sec in total
161 ms
7.1 sec
876 ms
Welcome to gogreenshine.com homepage info - get ready to check Go Green Shine best content right away, or after learning these important things about gogreenshine.com
Visit gogreenshine.comWe analyzed Gogreenshine.com page load time and found that the first response time was 161 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
gogreenshine.com performance score
name
value
score
weighting
Value12.4 s
0/100
10%
Value15.6 s
0/100
25%
Value29.6 s
0/100
10%
Value4,670 ms
0/100
30%
Value0.016
100/100
15%
Value34.0 s
0/100
10%
161 ms
1190 ms
271 ms
308 ms
206 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 95% of them (72 requests) were addressed to the original Gogreenshine.com, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Gogreenshine.com.
Page size can be reduced by 264.6 kB (10%)
2.5 MB
2.3 MB
In fact, the total size of Gogreenshine.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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 80.0 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 80.0 kB or 82% of the original size.
Potential reduce by 663 B
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. Go Green Shine images are well optimized though.
Potential reduce by 104.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 104.1 kB or 18% of the original size.
Potential reduce by 79.7 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. Gogreenshine.com needs all CSS files to be minified and compressed as it can save up to 79.7 kB or 42% of the original size.
Number of requests can be reduced by 54 (78%)
69
15
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Go Green Shine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
gogreenshine.com
161 ms
www.gogreenshine.com
1190 ms
styles.css
271 ms
eae.min.css
308 ms
peel.css
206 ms
v4-shims.min.css
192 ms
all.min.css
199 ms
vegas.min.css
243 ms
style.min.css
387 ms
theme.min.css
385 ms
frontend-lite.min.css
445 ms
post-7.css
428 ms
elementor-icons.min.css
456 ms
swiper.min.css
492 ms
frontend-lite.min.css
570 ms
global.css
573 ms
post-26.css
613 ms
post-28.css
628 ms
post-181.css
641 ms
css
27 ms
fontawesome.min.css
680 ms
solid.min.css
753 ms
brands.min.css
757 ms
iconHelper.js
800 ms
jquery.min.js
870 ms
jquery-migrate.min.js
828 ms
widget-nav-menu.min.css
868 ms
widget-icon-list.min.css
963 ms
animations.min.css
967 ms
index.js
966 ms
index.js
1028 ms
eae.min.js
1091 ms
index.min.js
1094 ms
v4-shims.min.js
1155 ms
animated-main.min.js
1159 ms
particles.min.js
1161 ms
magnific.min.js
1216 ms
vegas.min.js
1286 ms
api.js
39 ms
hello-frontend.min.js
1281 ms
wp-polyfill-inert.min.js
1246 ms
regenerator-runtime.min.js
1235 ms
wp-polyfill.min.js
1348 ms
index.js
1263 ms
jquery.smartmenus.min.js
1315 ms
imagesloaded.min.js
1266 ms
lottie.min.js
1388 ms
webpack-pro.runtime.min.js
1262 ms
webpack.runtime.min.js
1287 ms
frontend-modules.min.js
1353 ms
hooks.min.js
1313 ms
i18n.min.js
1297 ms
frontend.min.js
1262 ms
waypoints.min.js
1336 ms
core.min.js
1349 ms
frontend.min.js
1403 ms
elements-handlers.min.js
1327 ms
GreenShine-Source-00-00.png
1195 ms
GreenShine-Source-01-02.jpg
1290 ms
GreenShine-Source-01-03.jpg
1418 ms
GreenShine-Source-01-04.jpg
1533 ms
GreenShine-Source-01-05.png
1532 ms
GreenShine-Source-01-06.png
1316 ms
GreenShine-Source-01-07.jpg
1508 ms
font
20 ms
eicons.woff
1548 ms
fa-solid-900.woff
1588 ms
fa-regular-400.woff
1529 ms
fa-brands-400.woff
1658 ms
circle.svg
1487 ms
GreenShine-Source-01-08.jpg
1696 ms
GreenShine-Source-01-09.jpg
1657 ms
GreenShine-Source-01-10.jpg
1769 ms
GreenShine-Source-01-11.jpg
1752 ms
GreenShine-Source-01-12.jpg
1830 ms
recaptcha__en.js
32 ms
gogreenshine.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
gogreenshine.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
Page has valid source maps
gogreenshine.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
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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gogreenshine.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Gogreenshine.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.
gogreenshine.com
Open Graph description is not detected on the main page of Go Green Shine. 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: