975 ms in total
133 ms
585 ms
257 ms
Click here to check amazing Store Genderize content for India. Otherwise, check out these important facts you probably never knew about store.genderize.io
Use our API or CSV tool to infer gender from a name and check the certainty that it's male or female.
Visit store.genderize.ioWe analyzed Store.genderize.io page load time and found that the first response time was 133 ms and then it took 842 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
store.genderize.io performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value8.7 s
1/100
25%
Value5.7 s
51/100
10%
Value1,090 ms
24/100
30%
Value0.023
100/100
15%
Value8.8 s
36/100
10%
133 ms
99 ms
22 ms
37 ms
52 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 79% of them (30 requests) were addressed to the original Store.genderize.io, 11% (4 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (133 ms) belongs to the original domain Store.genderize.io.
Page size can be reduced by 867.5 kB (64%)
1.4 MB
487.3 kB
In fact, the total size of Store.genderize.io main page is 1.4 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. 35% of websites need less resources to load. CSS take 582.5 kB which makes up the majority of the site volume.
Potential reduce by 18.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 3.7 kB, which is 16% 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 18.3 kB or 82% of the original size.
Potential reduce by 19.7 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. Store Genderize images are well optimized though.
Potential reduce by 280.8 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 280.8 kB or 80% of the original size.
Potential reduce by 548.6 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. Store.genderize.io needs all CSS files to be minified and compressed as it can save up to 548.6 kB or 94% of the original size.
Number of requests can be reduced by 25 (81%)
31
6
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Store Genderize. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
store.genderize.io
133 ms
store.genderize.io
99 ms
modernizr.js
22 ms
prism.css
37 ms
styles.css
52 ms
crap.css
37 ms
jquery.min.js
80 ms
foundation.js
39 ms
foundation.abide.js
37 ms
foundation.accordion.js
37 ms
foundation.alert.js
38 ms
foundation.clearing.js
42 ms
foundation.dropdown.js
40 ms
foundation.interchange.js
40 ms
foundation.joyride.js
40 ms
foundation.magellan.js
43 ms
foundation.offcanvas.js
76 ms
foundation.orbit.js
76 ms
foundation.reveal.js
76 ms
foundation.tab.js
76 ms
foundation.tooltip.js
76 ms
foundation.topbar.js
76 ms
jquery.flot.js
79 ms
jquery.flot.time.js
78 ms
jquery.flot.threshold.js
77 ms
prism.js
78 ms
main.js
77 ms
css
47 ms
hero-bg.jpg
117 ms
dc.js
106 ms
bg-overlay2.png
53 ms
map.png
50 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
71 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
92 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
103 ms
cSd7NBXNFQWK4oX1706dYz8E0i7KZn-EPnyo3HZu7kw.woff
104 ms
icomoon.woff
26 ms
__utm.gif
12 ms
store.genderize.io 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
Image elements do not have [alt] attributes
store.genderize.io 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
Missing source maps for large first-party JavaScript
store.genderize.io SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Store.genderize.io can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Store.genderize.io 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.
store.genderize.io
Open Graph description is not detected on the main page of Store Genderize. 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: