Tools & Wizards About Us
oisto.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

oisto.com

IMEDSALES - Medical Equipment & Supplies

Page Load Speed

2.1 sec in total

First Response

34 ms

Resources Loaded

1.6 sec

Page Rendered

474 ms

oisto.com screenshot

About Website

Welcome to oisto.com homepage info - get ready to check Oisto best content right away, or after learning these important things about oisto.com

Visit oisto.com

Key Findings

We analyzed Oisto.com page load time and found that the first response time was 34 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

oisto.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value2,010 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value29.7 s

0/100

10%

Network Requests Diagram

oisto.com

34 ms

imedsales.com

73 ms

12e25d5b702a23f446c4507538df8c22.min.css

62 ms

styles-l.min.css

45 ms

56eb3ee624d55c79a7592548602eb711.min.js

31 ms

Our browser made a total of 183 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Oisto.com, 66% (121 requests) were made to Imedsales.com and 20% (37 requests) were made to Dkcdkv8eldsua.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Imedsales.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 298.3 kB (9%)

Content Size

3.1 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oisto.com main page is 3.1 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. 80% 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 292.1 kB

  • Original 318.3 kB
  • After minification 227.3 kB
  • After compression 26.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 91.0 kB, which is 29% 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 292.1 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 1.0 kB

  • Original 2.4 MB
  • After minification 2.4 MB

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. Oisto images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.9 kB

  • Original 255.2 kB
  • After minification 255.1 kB
  • After compression 252.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 2.3 kB

  • Original 139.0 kB
  • After minification 139.0 kB
  • After compression 136.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. Oisto.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 120 (77%)

Requests Now

156

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oisto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 108 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

oisto.com

oisto.com

34 ms

imedsales.com

imedsales.com

73 ms

12e25d5b702a23f446c4507538df8c22.min.css

12e25d5b702a23f446c4507538df8c22.min.css

62 ms

styles-l.min.css

styles-l.min.css

45 ms

56eb3ee624d55c79a7592548602eb711.min.js

56eb3ee624d55c79a7592548602eb711.min.js

31 ms

css

css

35 ms

css

css

52 ms

css

css

52 ms

css

css

53 ms

bootstrap.optimized.min.css

bootstrap.optimized.min.css

106 ms

animate.optimized.css

animate.optimized.css

144 ms

type2.css

type2.css

168 ms

custom.css

custom.css

114 ms

design_default.css

design_default.css

160 ms

settings_default.css

settings_default.css

112 ms

addthis_widget.js

addthis_widget.js

29 ms

default_0.js

default_0.js

243 ms

default_0_addition.js

default_0_addition.js

196 ms

jquery.min.js

jquery.min.js

30 ms

common.min.js

common.min.js

19 ms

dataPost.min.js

dataPost.min.js

18 ms

bootstrap.min.js

bootstrap.min.js

18 ms

app.min.js

app.min.js

26 ms

form-key-provider.min.js

form-key-provider.min.js

25 ms

mage-translation-dictionary.min.js

mage-translation-dictionary.min.js

1156 ms

theme.min.js

theme.min.js

36 ms

css2

css2

14 ms

template.min.js

template.min.js

21 ms

confirm.min.js

confirm.min.js

21 ms

widget.min.js

widget.min.js

22 ms

main.min.js

main.min.js

28 ms

bootstrap.min.js

bootstrap.min.js

28 ms

domReady.min.js

domReady.min.js

28 ms

jquery-mixin.min.js

jquery-mixin.min.js

26 ms

types.min.js

types.min.js

11 ms

layout.min.js

layout.min.js

11 ms

underscore.min.js

underscore.min.js

14 ms

translate.min.js

translate.min.js

13 ms

modal.min.js

modal.min.js

39 ms

smart-keyboard-handler.min.js

smart-keyboard-handler.min.js

36 ms

mage.min.js

mage.min.js

36 ms

knockout.min.js

knockout.min.js

45 ms

knockout-es5.min.js

knockout-es5.min.js

44 ms

wrapper.min.js

wrapper.min.js

41 ms

version.min.js

version.min.js

42 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

43 ms

scripts.min.js

scripts.min.js

41 ms

main.min.js

main.min.js

42 ms

registry.min.js

registry.min.js

42 ms

engine.min.js

engine.min.js

39 ms

bootstrap.min.js

bootstrap.min.js

39 ms

observable_array.min.js

observable_array.min.js

39 ms

bound-nodes.min.js

bound-nodes.min.js

40 ms

logo.png

logo.png

68 ms

shop4_header_phone.png

shop4_header_phone.png

68 ms

11.png

11.png

93 ms

22.png

22.png

68 ms

33.png

33.png

130 ms

44.png

44.png

170 ms

55.png

55.png

130 ms

66.png

66.png

171 ms

77.png

77.png

170 ms

shop4_cat1.jpg

shop4_cat1.jpg

170 ms

shop4_cat2.jpg

shop4_cat2.jpg

183 ms

shop4_cat3.jpg

shop4_cat3.jpg

174 ms

shop4_cat4.jpg

shop4_cat4.jpg

228 ms

shop4_cat5.jpg

shop4_cat5.jpg

226 ms

shop4_cat6.jpg

shop4_cat6.jpg

221 ms

5.png

5.png

258 ms

3.png

3.png

253 ms

1.jpg

1.jpg

234 ms

2.png

2.png

301 ms

12333.png

12333.png

232 ms

console-logger.min.js

console-logger.min.js

38 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

85 ms

opensans-400.woff

opensans-400.woff

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

98 ms

opensans-300.woff

opensans-300.woff

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

162 ms

opensans-600.woff

opensans-600.woff

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

123 ms

opensans-700.woff

opensans-700.woff

51 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

165 ms

text.min.js

text.min.js

57 ms

key-codes.min.js

key-codes.min.js

50 ms

core.min.js

core.min.js

1222 ms

z-index.min.js

z-index.min.js

82 ms

apear.min.js

apear.min.js

87 ms

jquery.sticky.min.js

jquery.sticky.min.js

76 ms

knockout-repeat.min.js

knockout-repeat.min.js

54 ms

knockout-fast-foreach.min.js

knockout-fast-foreach.min.js

89 ms

events.min.js

events.min.js

89 ms

arrays.min.js

arrays.min.js

83 ms

compare.min.js

compare.min.js

124 ms

misc.min.js

misc.min.js

123 ms

objects.min.js

objects.min.js

121 ms

strings.min.js

strings.min.js

123 ms

template.min.js

template.min.js

137 ms

observable_source.min.js

observable_source.min.js

135 ms

renderer.min.js

renderer.min.js

137 ms

resizable.min.js

resizable.min.js

135 ms

i18n.min.js

i18n.min.js

171 ms

scope.min.js

scope.min.js

170 ms

range.min.js

range.min.js

171 ms

mage-init.min.js

mage-init.min.js

169 ms

keyboard.min.js

keyboard.min.js

172 ms

optgroup.min.js

optgroup.min.js

173 ms

after-render.min.js

after-render.min.js

171 ms

autoselect.min.js

autoselect.min.js

172 ms

local.min.js

local.min.js

172 ms

datepicker.min.js

datepicker.min.js

171 ms

outer_click.min.js

outer_click.min.js

172 ms

fadeVisible.min.js

fadeVisible.min.js

172 ms

collapsible.min.js

collapsible.min.js

172 ms

staticChecked.min.js

staticChecked.min.js

174 ms

simple-checked.min.js

simple-checked.min.js

173 ms

bind-html.min.js

bind-html.min.js

169 ms

tooltip.min.js

tooltip.min.js

171 ms

color-picker.min.js

color-picker.min.js

166 ms

logger.min.js

logger.min.js

164 ms

entry-factory.min.js

entry-factory.min.js

138 ms

console-output-handler.min.js

console-output-handler.min.js

139 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

75 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

73 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

78 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

80 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

82 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

80 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

82 ms

formatter.min.js

formatter.min.js

136 ms

message-pool.min.js

message-pool.min.js

105 ms

levels-pool.min.js

levels-pool.min.js

103 ms

logger-utils.min.js

logger-utils.min.js

125 ms

modal-popup.html

modal-popup.html

125 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

47 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

48 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

51 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

49 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

49 ms

menu-banner1_1_.jpg

menu-banner1_1_.jpg

132 ms

modal-slide.html

modal-slide.html

87 ms

modal-custom.html

modal-custom.html

86 ms

fa-brands-400.woff

fa-brands-400.woff

86 ms

porto-icons.woff

porto-icons.woff

87 ms

animate.min.js

animate.min.js

73 ms

sw_megamenu.min.js

sw_megamenu.min.js

46 ms

class.min.js

class.min.js

44 ms

async.min.js

async.min.js

44 ms

loader.min.js

loader.min.js

55 ms

tooltip.html

tooltip.html

53 ms

spectrum.min.js

spectrum.min.js

54 ms

tinycolor.min.js

tinycolor.min.js

52 ms

moment.min.js

moment.min.js

54 ms

entry.min.js

entry.min.js

35 ms

dom-observer.min.js

dom-observer.min.js

15 ms

bindings.min.js

bindings.min.js

13 ms

owl.carousel.min.js

owl.carousel.min.js

20 ms

shop4_home_banner.jpg

shop4_home_banner.jpg

319 ms

shop4_home_banner2_1_1_.jpg

shop4_home_banner2_1_1_.jpg

308 ms

shop4_home_slider_1_1_.jpg

shop4_home_slider_1_1_.jpg

114 ms

shop4_home_slider_2.jpg

shop4_home_slider_2.jpg

114 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

57 ms

payment-visa.svg

payment-visa.svg

132 ms

payment-paypal.svg

payment-paypal.svg

83 ms

payment-stripe.png

payment-stripe.png

86 ms

payment-verisign.svg

payment-verisign.svg

83 ms

js-translation.json

js-translation.json

67 ms

UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD8.ttf

UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD8.ttf

5 ms

print.min.css

print.min.css

11 ms

data.min.js

data.min.js

16 ms

disable-selection.min.js

disable-selection.min.js

16 ms

focusable.min.js

focusable.min.js

17 ms

form.min.js

form.min.js

16 ms

ie.min.js

ie.min.js

17 ms

keycode.min.js

keycode.min.js

19 ms

labels.min.js

labels.min.js

19 ms

jquery-patch.min.js

jquery-patch.min.js

19 ms

plugin.min.js

plugin.min.js

20 ms

safe-active-element.min.js

safe-active-element.min.js

19 ms

safe-blur.min.js

safe-blur.min.js

19 ms

scroll-parent.min.js

scroll-parent.min.js

23 ms

tabbable.min.js

tabbable.min.js

23 ms

unique-id.min.js

unique-id.min.js

24 ms

Accessibility Review

oisto.com accessibility score

79

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

oisto.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

oisto.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oisto.com 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 Oisto.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.

Social Sharing Optimization

oisto.com

Open Graph description is not detected on the main page of Oisto. 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: