Tools & Wizards About Us
sdataway.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

sdataway.com

SDATAWAY SA - Bureau d'ingénieurs, développement électronique et logiciel

Page Load Speed

7.5 sec in total

First Response

1.4 sec

Resources Loaded

5.9 sec

Page Rendered

175 ms

sdataway.com screenshot

About Website

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

Bureau d’ingénieurs basé en Suisse, spécialisé dans l'innovation et le développement sur mesure de solution électronique et logiciel.

Visit sdataway.com

Key Findings

We analyzed Sdataway.com page load time and found that the first response time was 1.4 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

sdataway.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.356

30/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

www.sdataway.com

1446 ms

twemoji.js

102 ms

wp-emoji.js

203 ms

dashicons.css

391 ms

extra.css

293 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 86% of them (72 requests) were addressed to the original Sdataway.com, 7% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Sdataway.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 289.8 kB (6%)

Content Size

5.0 MB

After Optimization

4.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sdataway.com main page is 5.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. 55% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 48.3 kB

  • Original 60.8 kB
  • After minification 59.8 kB
  • After compression 12.5 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 48.3 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 192.9 kB

  • Original 4.4 MB
  • After minification 4.2 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. SDATAWAY images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 38.6 kB

  • Original 423.3 kB
  • After minification 423.3 kB
  • After compression 384.7 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

-9%

Potential reduce by 10.0 kB

  • Original 110.9 kB
  • After minification 110.9 kB
  • After compression 100.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. Sdataway.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 49 (64%)

Requests Now

76

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SDATAWAY. 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 21 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.sdataway.com

www.sdataway.com

1446 ms

twemoji.js

twemoji.js

102 ms

wp-emoji.js

wp-emoji.js

203 ms

dashicons.css

dashicons.css

391 ms

extra.css

extra.css

293 ms

style.css

style.css

298 ms

styles.css

styles.css

296 ms

styles.css

styles.css

295 ms

front_custom_style.css

front_custom_style.css

300 ms

style.min.css

style.min.css

391 ms

style.min.css

style.min.css

393 ms

style.css

style.css

398 ms

css

css

31 ms

superfish.css

superfish.css

393 ms

component.css

component.css

397 ms

font-awesome.min.css

font-awesome.min.css

489 ms

style.css

style.css

490 ms

jquery.fancybox.css

jquery.fancybox.css

492 ms

flexslider.css

flexslider.css

491 ms

style-responsive.css

style-responsive.css

495 ms

style-custom.css

style-custom.css

497 ms

masterslider.main.css

masterslider.main.css

590 ms

custom.css

custom.css

588 ms

jquery.js

jquery.js

793 ms

jquery-migrate.js

jquery-migrate.js

597 ms

js

js

85 ms

wp-polyfill.js

wp-polyfill.js

699 ms

index.js

index.js

597 ms

superfish.js

superfish.js

689 ms

hoverIntent.js

hoverIntent.js

687 ms

modernizr.custom.js

modernizr.custom.js

690 ms

jquery.dlmenu.js

jquery.dlmenu.js

695 ms

jquery.easing.js

jquery.easing.js

786 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

787 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

789 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

831 ms

jquery.flexslider.js

jquery.flexslider.js

831 ms

gdlr-script.js

gdlr-script.js

923 ms

masterslider.min.js

masterslider.min.js

1059 ms

wp-embed.js

wp-embed.js

827 ms

jquery.isotope.min.js

jquery.isotope.min.js

728 ms

jquery.transit.min.js

jquery.transit.min.js

638 ms

gdlr-portfolio-script.js

gdlr-portfolio-script.js

634 ms

analytics.js

analytics.js

62 ms

logo-SDATAWAY_252x120.png

logo-SDATAWAY_252x120.png

253 ms

en.png

en.png

253 ms

magnifier-dark.png

magnifier-dark.png

254 ms

blank.gif

blank.gif

254 ms

LaurastarSmart.jpg

LaurastarSmart.jpg

312 ms

IMAGE-EASYBUS3-POUR-SITE-INTERNET.png

IMAGE-EASYBUS3-POUR-SITE-INTERNET.png

601 ms

easy.png

easy.png

310 ms

coclock-by_SDATAWAY-300x95.png

coclock-by_SDATAWAY-300x95.png

311 ms

ampoule.png

ampoule.png

312 ms

logo-IOT-sDATA-BLUESDATA-SITE-INTERNET-1.png

logo-IOT-sDATA-BLUESDATA-SITE-INTERNET-1.png

313 ms

electronique.png

electronique.png

408 ms

software.png

software.png

410 ms

protoypage.png

protoypage.png

408 ms

industrialisation.png

industrialisation.png

409 ms

DSC0091-scaled.jpg

DSC0091-scaled.jpg

509 ms

adhoco_v2_lowres.jpg

adhoco_v2_lowres.jpg

795 ms

shako_1_lowres.jpg

shako_1_lowres.jpg

798 ms

tesa_2_lowres.jpg

tesa_2_lowres.jpg

707 ms

dolcegusto_1_lowres.jpg

dolcegusto_1_lowres.jpg

804 ms

asyril_1_lowres.jpg

asyril_1_lowres.jpg

806 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

91 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

98 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

104 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

104 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

640 ms

wp-polyfill-fetch.js

wp-polyfill-fetch.js

716 ms

wp-polyfill-dom-rect.js

wp-polyfill-dom-rect.js

724 ms

wp-polyfill-url.js

wp-polyfill-url.js

815 ms

wp-polyfill-formdata.js

wp-polyfill-formdata.js

823 ms

wp-polyfill-element-closest.js

wp-polyfill-element-closest.js

825 ms

wp-polyfill-object-fit.js

wp-polyfill-object-fit.js

836 ms

collect

collect

30 ms

js

js

64 ms

css

css

17 ms

loading-2.gif

loading-2.gif

99 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

42 ms

master-slider-right.png

master-slider-right.png

99 ms

master-slider-left.png

master-slider-left.png

101 ms

header_1.jpg

header_1.jpg

197 ms

Accessibility Review

sdataway.com accessibility score

91

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

sdataway.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

sdataway.com SEO score

91

Search Engine Optimization Advices

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sdataway.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Sdataway.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

sdataway.com

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