3.8 sec in total
117 ms
3.4 sec
282 ms
Welcome to gemmyplanet.com homepage info - get ready to check Gemmyplanet best content right away, or after learning these important things about gemmyplanet.com
Visit gemmyplanet.comWe analyzed Gemmyplanet.com page load time and found that the first response time was 117 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
gemmyplanet.com performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value2.3 s
94/100
25%
Value2.7 s
96/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value2.5 s
98/100
10%
117 ms
93 ms
128 ms
162 ms
167 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Gemmyplanet.com, 40% (34 requests) were made to Static.parastorage.com and 29% (24 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.7 MB (74%)
3.6 MB
942.2 kB
In fact, the total size of Gemmyplanet.com main page is 3.6 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. 75% 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. Javascripts take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 131.1 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 131.1 kB or 85% of the original size.
Potential reduce by 17.3 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. Gemmyplanet images are well optimized though.
Potential reduce by 2.3 MB
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 2.3 MB or 76% of the original size.
Potential reduce by 246.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. Gemmyplanet.com needs all CSS files to be minified and compressed as it can save up to 246.7 kB or 83% of the original size.
Number of requests can be reduced by 50 (63%)
80
30
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gemmyplanet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
gemmyplanet.com
117 ms
www.gemmyplanet.com
93 ms
bt
128 ms
require.min.js
162 ms
main-r.min.js
167 ms
viewer.css
193 ms
UpgradeBrowser.js
196 ms
ugc-viewer
81 ms
dynamicmodel
76 ms
38dd51_cd58bf408091630bce20d802479fe884_53.json.z
687 ms
38dd51_63721bb314d221a19541186564041422_50.json.z
722 ms
bt
124 ms
skins.min.js
252 ms
components.min.js
250 ms
utils.min.js
99 ms
core.min.js
95 ms
react-with-addons.min.js
98 ms
lodash.min.js
97 ms
TweenMax.min.js
245 ms
layout.min.js
242 ms
tpa.min.js
239 ms
fonts.min.js
237 ms
animations.min.js
239 ms
swfobject.min.js
421 ms
mousetrap.min.js
422 ms
tweenEngine.min.js
420 ms
DrawSVGPlugin.min.js
418 ms
react-dom.min.js
419 ms
ScrollToPlugin.min.js
417 ms
widgets.min.js
418 ms
experiment.js
419 ms
render.min.js
413 ms
wixappsCore.min.js
418 ms
wixappsClassics.min.js
419 ms
wixappsBuilder.min.js
414 ms
zepto.min.js
409 ms
color.min.js
408 ms
react-dom-server.min.js
164 ms
bt
179 ms
bt
705 ms
mobileIEFix.css
349 ms
css
346 ms
latin.css
343 ms
pixel.gif
385 ms
41d000_b9c282164ac44282819f2131ae4a0ff0.png
158 ms
41d000_f6c62d1674b84613a93b06dfe60a0311.png
158 ms
4f857b2e8a316c4e1ed16717a3d4ec8c.png
347 ms
89b1d2497b29ccbb7d37be1ec6ef0052.png
348 ms
4ff0ed15574b046b9b7596cd38cbc759.png
396 ms
38dd51_e66167c3f29d46aa8143e9e987284be7.gif
864 ms
38dd51_3a886d330d9b49fabb3e587d8892028c.gif
862 ms
38dd51_8d367de35d3645149eba4d0ac06d697c.gif
792 ms
38dd51_a072868f053745f9b66e5c904367c2f8.gif
789 ms
38dd51_93cf36acf82340d3b9c0dba2d2fe72bb.gif
616 ms
38dd51_ba8505a6e2d84246b724df11d241b71a.png
853 ms
38dd51_d05ca8c7984e49cbaabd942ced87396b.gif
915 ms
38dd51_773923f1eb6f4b2fa66ea332a68a9b8b.gif
855 ms
41d000_10620c8275074793a75e95ab60853ff9.png
854 ms
41d000_d79133a5fd8a43c898adb7f9570873c7.png
861 ms
41d000_b1a6b395934de037c98bf23b0b17bc85.gif
863 ms
38dd51_4749681197ea4722bd4230ee36550e0a.gif
1177 ms
38dd51_838009174ce54e79ab1b3e307da72fe4.gif
1162 ms
41d000_9f073caef672431687159b47d5b94bd1.png
914 ms
38dd51_b9e96a10d62f42489e15da40acb35b4a.jpg
1043 ms
576c15d89bd3966447f19d7a92729323.wix_mp
1242 ms
bt
180 ms
bt
180 ms
bt
380 ms
shiny1button_bg.png
136 ms
dc.js
342 ms
RiS2B-HyiOk
355 ms
gK3Lvigl338
401 ms
like.php
448 ms
e947b76a-edcf-4519-bc3d-c2da35865717.woff
35 ms
btn_buynowCC_LG.gif
213 ms
576c15d89bd3966447f19d7a92729323.wix_mp
653 ms
ugc-viewer
53 ms
__utm.gif
19 ms
www-embed-player-vflRGs1ko.css
103 ms
www-embed-player.js
190 ms
fy8tT2klpgR.js
381 ms
LVx-xkvaJ0b.png
386 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
153 ms
ad_status.js
160 ms
gemmyplanet.com accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
gemmyplanet.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
gemmyplanet.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gemmyplanet.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gemmyplanet.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.
gemmyplanet.com
Open Graph description is not detected on the main page of Gemmyplanet. 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: