2.5 sec in total
195 ms
1.8 sec
555 ms
Click here to check amazing Stor content for United States. Otherwise, check out these important facts you probably never knew about stor.re
A/B test your App Store or Google Play page and discover the most converting icon, screenshots, video app preview for mobile app or game, improve ROI and get more installs.
Visit stor.reWe analyzed Stor.re page load time and found that the first response time was 195 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
stor.re performance score
195 ms
130 ms
110 ms
243 ms
34 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Stor.re, 9% (9 requests) were made to Apis.google.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (815 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 524.1 kB (24%)
2.2 MB
1.7 MB
In fact, the total size of Stor.re main page is 2.2 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. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 47.8 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 47.8 kB or 77% of the original size.
Potential reduce by 33.8 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. Stor images are well optimized though.
Potential reduce by 338.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 338.4 kB or 67% of the original size.
Potential reduce by 104.2 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. Stor.re needs all CSS files to be minified and compressed as it can save up to 104.2 kB or 81% of the original size.
Number of requests can be reduced by 46 (55%)
83
37
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stor. 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 6 to 1 for CSS and as a result speed up the page load time.
splitmetrics.com
195 ms
fbevents.js
130 ms
heap-1715733034.js
110 ms
vlh1jpo.js
243 ms
bean-shortcodes.css
34 ms
jquery.js
120 ms
jquery-migrate.min.js
98 ms
all.css
119 ms
home-header.jpg
123 ms
f1bb133fedffaef33a1551835bba39c02693d43f.js
117 ms
custom-libraries.js
118 ms
custom.js
78 ms
retina.js
87 ms
comment-reply.min.js
116 ms
jquery.validate.min.js
136 ms
post-likes.js
120 ms
bean-shortcodes.min.js
120 ms
email-subscription.js
120 ms
count.js
120 ms
bootstrap.js
125 ms
jquery.autocomplete.min.js
126 ms
jquery.sticky.js
126 ms
jquery.magnific-popup.min.js
124 ms
splitmetrics.custom.js
125 ms
platform.js
114 ms
106 ms
bootstrap.css
14 ms
a
815 ms
sdk.js
82 ms
badge_light.png
231 ms
logo.svg
51 ms
logo-white.svg
48 ms
promo-home-bg.jpg
53 ms
search-loader.gif
50 ms
rovio-sp.png
51 ms
fiftythree-sp.png
52 ms
mycom-sp.png
62 ms
wargaming-sp.png
61 ms
zeptolab-sp.png
62 ms
outfit7-inactive.png
62 ms
plarium-inactive.png
62 ms
rovio.png
61 ms
fiftythree.jpg
100 ms
mycom.jpg
121 ms
wargaming.jpg
98 ms
zeptolab.jpg
119 ms
phone.png
84 ms
test-params-icons-and-screenshots.jpg
85 ms
analytics-report-01.jpg
96 ms
analytics-report-02.jpg
90 ms
analytics-report-03.jpg
97 ms
coursera-ab-test-google-play.png
125 ms
abtesting_icons_splitmetrics-1024x659.jpg
117 ms
spriteSeenOn.png
115 ms
widgets.js
64 ms
counter.js
86 ms
84 ms
xd_arbiter.php
339 ms
join
198 ms
t.php
638 ms
analytics.js
84 ms
css
84 ms
popup_image2.jpg
80 ms
collect
52 ms
count.js
178 ms
collect
263 ms
cb=gapi.loaded_0
118 ms
cb=gapi.loaded_1
160 ms
follow
235 ms
gtm.js
220 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
28 ms
h
390 ms
like.php
160 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
162 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
167 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
380 ms
wAAABAAAAAAABAAAAQAAAAAAAAAAAAAAAAAAAAcAAAAAAAAAAAAAAAACAAAABAAAOAQAAAAEAAAAAAAAAAAKABQAHgBmAKYA5gABAAAABwAuAAIAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADgAAAAEAAAAAAAIADgBHAAEAAAAAAAMADgAkAAEAAAAAAAQADgBVAAEAAAAAAAUAFgAOAAEAAAAAAAYABwAyAAEAAAAAAAoANABjAAMAAQQJAAEADgAAAAMAAQQJAAIADgBHAAMAAQQJAAMADgAkAAMAAQQJAAQADgBVAAMAAQQJAAUAFgAOAAMAAQQJAAYADgA5AAMAAQQJAAoANABjAGkAYwBvAG0AbwBvAG4AVgBlAHIAcwBpAG8AbgAgADEALgAwAGkAYwBvAG0AbwBvAG5pY29tb29uAGkAYwBvAG0AbwBvAG4AUgBlAGcAdQBsAGEAcgBpAGMAbwBtAG8AbwBuAEYAbwBuAHQAIABnAGUAbgBlAHIAYQB0AGUAZAAgAGIAeQAgAEkAYwBvAE0AbwBvAG4ALgAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
17 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
88 ms
postmessageRelay
275 ms
qeKvIRsJabD.js
537 ms
LVx-xkvaJ0b.png
573 ms
rs=AGLTcCPaIpnvYdvK9nEPlKCC4baoCWq5dw
30 ms
rs=AGLTcCP1XWuWX_iCC9WgWr0vKsRUFWxeag
29 ms
rs=AGLTcCOYYgQ3JxVNs4OscPZY6LDahwt1EA
29 ms
ga-audiences
367 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
142 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
117 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
142 ms
jot
192 ms
3193398744-postmessagerelay.js
147 ms
rpc:shindig_random.js
106 ms
twAAAAAAAAAAAAAAAAAAAAAAAOAaAADfxd+KIIMgBCAOIBcgJiAqAAEAOAAAAFQAAACCAAAAigAAAIgAjgFMAU4BTgFOAVABUgFWAAABVAAAAAAAAAAAAAAAAAAAAAAAAAABAEMAbwB1AHIAgQDMAG4AWgBbAGYAdwA8AEEAPwBTAD4APQB8AHsAfQDIAM0AAgCDAAMABAAFAAYABwAIAAkAlAAKAAsADAANAA4AywAPAJsAXgBsAF8AaQBtADQAggBiAFQAYwBqAAEARACtAHMArgB0AGsAZwA4AHAAtQBPAH4AfwCzADkAgAB4AOoA6wA1ALcAaAC0ADsA0AC2AFEAzgDsAO0ARgCEAIUAhgCHAIgAiQCwAIoAjACNAI4AjwCQAJEAkgCTAPUAlQCWAJcAmACZAJoAeQCyAJwAnQCeAJ8AoAAYAMAA0QDSANMA1ADVANYArwCiAKMApAClAKYApwCoAKkAqgAzALgAuQC6ALsAvAC9AHoAvgDBAMIAwwDEAMUA3wDGALEAvwChADcAVQBXAEgASQDJAEoAygBZAEsATQAA
21 ms
tgAAAAAAAAAAAAAAAAAAAAAAAOAZAADfxN+JIIIgBCAOIBcgJSApAAEANAAAAFAAAAB+AAAApACqAWgBagFqAWoBbAFuAXIAAAFwAAAAAAAAAAAAAAAAAAAAAAAAAAEAQgBuAHQAcQCAAMsAbQBZAFoAZQB2ADsAQAA+AFIAPQA8AHsAegB8AMcAzAACAIIAAwAEAAUABgAHAAgACQCTAAoACwAMAA0ADgDKAA8AmgBdAGsAXgBoAGwAMwAZABoAGwAcAB0AHgDzAB8AIAAhACIAIwAkACUAgQBhAFMAYgBpAAEAQwCsAHIArQBzAGoAZgA3AG8AtABOAH0AfgCyADgAfwB3AOkA6gA0ALYAZwCzADoAzwC1AFAAzQDrAOwARQCDAIQAhQCGAIcAiACvAIkAiwCMAI0AjgCPAJAAkQCSAPIAlACVAJYAlwCYAJkAeACxAJsAnACdAJ4AnwAYAL8A0ADRANIA0wDUANUArgChAKIAowCkAKUApgCnAKgAqQAyALcAuAC5ALoAuwC8AHkAvQDAAMEAwgDDAMQA3gDFALAAvgCgADYAVABWAEcASADIAEkAyQBYAEoATAAA
19 ms
p.gif
138 ms
cb=gapi.loaded_0
9 ms
2626641faa2a4f4ba023e0963a748acb8da1d793df49477caa41be8fb4387f50
126 ms
stor.re SEO score
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stor.re 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 Stor.re 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.
stor.re
Open Graph data is detected on the main page of Stor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: