3.2 sec in total
146 ms
2.7 sec
286 ms
Welcome to instastore.com.br homepage info - get ready to check Instastore best content right away, or after learning these important things about instastore.com.br
Aqui na Society Print você personaliza produtos incríveis com suas fotos favoritas do Instagram, Facebook e computador.
Visit instastore.com.brWe analyzed Instastore.com.br page load time and found that the first response time was 146 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
instastore.com.br performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.2 s
73/100
25%
Value3.2 s
92/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value3.2 s
94/100
10%
146 ms
194 ms
13 ms
9 ms
7 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 48% of them (26 requests) were addressed to the original Instastore.com.br, 6% (3 requests) were made to Static.olark.com and 6% (3 requests) were made to Pixel-geo.prfct.co. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Instastore.com.br.
Page size can be reduced by 347.6 kB (38%)
912.3 kB
564.7 kB
In fact, the total size of Instastore.com.br main page is 912.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 463.0 kB which makes up the majority of the site volume.
Potential reduce by 20.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 14% 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 20.3 kB or 74% of the original size.
Potential reduce by 13.2 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. Instastore images are well optimized though.
Potential reduce by 161.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 161.1 kB or 66% of the original size.
Potential reduce by 152.9 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. Instastore.com.br needs all CSS files to be minified and compressed as it can save up to 152.9 kB or 85% of the original size.
Number of requests can be reduced by 31 (66%)
47
16
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Instastore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
instastore.com.br
146 ms
www.instastore.com.br
194 ms
bootstrap.css
13 ms
bootstrap-responsive.css
9 ms
yiistrap.css
7 ms
fonts.css
813 ms
common.css
1822 ms
style.css
1824 ms
jquery.js
16 ms
scripts.js
14 ms
bootstrap.js
13 ms
dc.js
56 ms
sdk.js
169 ms
logotipo.png
42 ms
header-cores.jpg
42 ms
webdoor-7.jpg
46 ms
photos.jpg
47 ms
instacards.jpg
45 ms
instaposter.jpg
42 ms
imas.jpg
41 ms
squares.jpg
46 ms
passos.png
45 ms
logos-redes.png
41 ms
logotipo-pagseguro.png
42 ms
logotipo-paypal.png
42 ms
d8278225-8747-4e8b-a0fe-d9b70dbcbd43.js
36 ms
museosans_700-webfont.woff
16 ms
museosans_300-webfont.woff
16 ms
museosans_500-webfont.woff
16 ms
__utm.gif
14 ms
WRf4.js
3 ms
5231dc7f7b565a732100006d.js
17 ms
fbds.js
123 ms
loader0.js
95 ms
tagjs
30 ms
70 ms
adsct
182 ms
Pug
120 ms
pixel
114 ms
1959-383-10-9699.js
58 ms
169 ms
xd_arbiter.php
159 ms
xd_arbiter.php
284 ms
125 ms
cb
67 ms
c
154 ms
pixel
25 ms
sd
15 ms
tap.php
41 ms
cb
5 ms
ncm
4 ms
cb
5 ms
application2.js
115 ms
25 ms
instastore.com.br 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
Document doesn't have a <title> element
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
instastore.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
instastore.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Instastore.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Instastore.com.br 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.
instastore.com.br
Open Graph description is not detected on the main page of Instastore. 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: