1.7 sec in total
160 ms
1.4 sec
150 ms
Click here to check amazing Storemed content. Otherwise, check out these important facts you probably never knew about storemed.com
Website for Storemed
Visit storemed.comWe analyzed Storemed.com page load time and found that the first response time was 160 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
storemed.com performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value7.5 s
4/100
25%
Value2.8 s
96/100
10%
Value1,250 ms
19/100
30%
Value0.003
100/100
15%
Value7.4 s
49/100
10%
160 ms
38 ms
113 ms
64 ms
68 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Storemed.com, 62% (38 requests) were made to Static.parastorage.com and 15% (9 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (447 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.2 MB (73%)
3.0 MB
803.3 kB
In fact, the total size of Storemed.com main page is 3.0 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 28 B
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 28 B or 19% of the original size.
Potential reduce by 9.1 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. Storemed images are well optimized though.
Potential reduce by 2.1 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.1 MB or 77% of the original size.
Potential reduce by 64.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. Storemed.com needs all CSS files to be minified and compressed as it can save up to 64.6 kB or 85% of the original size.
Number of requests can be reduced by 42 (76%)
55
13
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Storemed. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
storemed.com
160 ms
-storemed
38 ms
bt
113 ms
require.min.js
64 ms
main-r.min.js
68 ms
viewer.css
89 ms
UpgradeBrowser.js
91 ms
dynamicmodel
17 ms
fa74da_017e511beb596d3d46fe3c179ea65e31_16.json.z
401 ms
fa74da_32479322020d305cc3c14fca1f998633_15.json.z
447 ms
ugc-viewer
147 ms
bt
158 ms
skins.min.js
151 ms
components.min.js
53 ms
utils.min.js
137 ms
core.min.js
50 ms
react-with-addons.min.js
135 ms
lodash.min.js
134 ms
TweenMax.min.js
140 ms
layout.min.js
143 ms
tpa.min.js
136 ms
fonts.min.js
134 ms
animations.min.js
133 ms
swfobject.min.js
136 ms
mousetrap.min.js
135 ms
tweenEngine.min.js
133 ms
DrawSVGPlugin.min.js
136 ms
react-dom.min.js
138 ms
ScrollToPlugin.min.js
137 ms
widgets.min.js
139 ms
experiment.js
140 ms
render.min.js
367 ms
wixappsCore.min.js
141 ms
wixappsClassics.min.js
368 ms
wixappsBuilder.min.js
139 ms
zepto.min.js
139 ms
color.min.js
136 ms
react-dom-server.min.js
249 ms
bt
60 ms
latin.css
43 ms
dc.js
287 ms
bt
271 ms
hebrew.css
251 ms
d75821b3625d16f95dfd8ebff761922d.png
172 ms
mobileIEFix.css
142 ms
wf_label_static.png
60 ms
BG91x1.jpg
79 ms
arrows_white_new3.png
59 ms
09b721261e9fba8dd8a96ee539a0743f.png
73 ms
058dcec0ee7cae49a2f9cbbc64848d0f.png
60 ms
fa74da_ee1e1c4cf0884a468fd0be7a967c51bd.jpg
332 ms
fa74da_07aba46ab06f43de93dd6e8b5483bc69.jpg
299 ms
fa74da_ff672ad01a6c42e2b3888439a705865e.jpg
325 ms
bt
78 ms
bt
81 ms
bt
76 ms
bc176270-17fa-4c78-a343-9fe52824e501.woff
59 ms
__utm.gif
32 ms
ga-audiences
63 ms
arabic.css
37 ms
ugc-viewer
49 ms
storemed.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
storemed.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
storemed.com SEO score
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
Tap targets are not sized appropriately
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Storemed.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 Storemed.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
storemed.com
Open Graph description is not detected on the main page of Storemed. 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: