Tools & Wizards About Us
w4store.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% 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

  • 77

    SEO

    Google-friendlier than
    36% of websites

w4store.com

Social Business Process Applications plateform | ITESOFT ECOSYSTEM

Page Load Speed

2.6 sec in total

First Response

235 ms

Resources Loaded

2.2 sec

Page Rendered

186 ms

w4store.com screenshot

About Website

Visit w4store.com now to see the best up-to-date W 4 Store content and also check out these interesting facts you probably never knew about w4store.com

ITESOFT ECOSYSTEM is a community platform to help you in your projects. Ie, W4 Web Modeler will help you to model and share your bpmn processes.

Visit w4store.com

Key Findings

We analyzed W4store.com page load time and found that the first response time was 235 ms and then it took 2.4 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.

Performance Metrics

w4store.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

w4store.com

235 ms

ecosystem.itesoft.com

544 ms

system.base.css

88 ms

system.menus.theme.css

176 ms

system.messages.theme.css

255 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original W4store.com, 98% (65 requests) were made to Ecosystem.itesoft.com. The less responsive or slowest element that took the longest time to load (762 ms) relates to the external source Ecosystem.itesoft.com.

Page Optimization Overview & Recommendations

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

Content Size

300.0 kB

After Optimization

273.2 kB

  • HTML
  • Images

In fact, the total size of W4store.com main page is 300.0 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. 35% of websites need less resources to load. Images take 277.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 17.9 kB

  • Original 22.7 kB
  • After minification 21.2 kB
  • After compression 4.9 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 17.9 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 9.0 kB

  • Original 277.3 kB
  • After minification 268.3 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. W 4 Store images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 40 (68%)

Requests Now

59

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

w4store.com

w4store.com

235 ms

ecosystem.itesoft.com

ecosystem.itesoft.com

544 ms

system.base.css

system.base.css

88 ms

system.menus.theme.css

system.menus.theme.css

176 ms

system.messages.theme.css

system.messages.theme.css

255 ms

system.theme.css

system.theme.css

256 ms

datepicker.1.7.css

datepicker.1.7.css

263 ms

comment.css

comment.css

261 ms

date_repeat_field.css

date_repeat_field.css

263 ms

field.theme.css

field.theme.css

340 ms

user.base.css

user.base.css

339 ms

forum.theme.css

forum.theme.css

348 ms

user.theme.css

user.theme.css

349 ms

region_header.WXWnpOitU_f618rCshfksKPK2jHQCqd22RSuC5bi1dk.css

region_header.WXWnpOitU_f618rCshfksKPK2jHQCqd22RSuC5bi1dk.css

350 ms

ckeditor.css

ckeditor.css

422 ms

ctools.css

ctools.css

423 ms

panels.css

panels.css

430 ms

home.-IcGUwLK9_9pkFv-ps6__WKIKUy6F_mvjAf_brd2eKc.css

home.-IcGUwLK9_9pkFv-ps6__WKIKUy6F_mvjAf_brd2eKc.css

434 ms

region_messages.y0YmZvFGV4VNdKxuvMJP4w_a7Z_-ZHd8V8pnT50oNz8.css

region_messages.y0YmZvFGV4VNdKxuvMJP4w_a7Z_-ZHd8V8pnT50oNz8.css

435 ms

addtoany.css

addtoany.css

437 ms

region_footer.QQ4fCNeuoj6nvQvyXR1rke8fVno1lg5MUUMdvYTh_os.css

region_footer.QQ4fCNeuoj6nvQvyXR1rke8fVno1lg5MUUMdvYTh_os.css

507 ms

region_side.FBUllXWoaqLBlxqIdHSXHKCzmXDDqqUO-eLQB622DBw.css

region_side.FBUllXWoaqLBlxqIdHSXHKCzmXDDqqUO-eLQB622DBw.css

506 ms

supersimple.layout.Ur3VODxfPxdzApoGgIizNQHMlpTQdEOQB-gQoRWtGdM.css

supersimple.layout.Ur3VODxfPxdzApoGgIizNQHMlpTQdEOQB-gQoRWtGdM.css

517 ms

w4theme.normalize.Wc0tpMbQZFLiNQyUMDp4M2oxFAYsTQP328aiBC6mTAw.css

w4theme.normalize.Wc0tpMbQZFLiNQyUMDp4M2oxFAYsTQP328aiBC6mTAw.css

520 ms

w4theme.styles.73279m3pvGhONFdQNQK82HDDmp6TB_W3uqD_kwMwYTc.css

w4theme.styles.73279m3pvGhONFdQNQK82HDDmp6TB_W3uqD_kwMwYTc.css

522 ms

jquery.fancybox.css

jquery.fancybox.css

524 ms

ihover.css

ihover.css

594 ms

jquery.min.js

jquery.min.js

679 ms

jquery.once.js

jquery.once.js

603 ms

drupal.js

drupal.js

607 ms

no-js.js

no-js.js

609 ms

en_US_lokE4Q-lFYbX0U9Wk4bBZE_OUYbv7b2JCxYd21kxukI.js

en_US_lokE4Q-lFYbX0U9Wk4bBZE_OUYbv7b2JCxYd21kxukI.js

611 ms

region_messages.js

region_messages.js

678 ms

region_header.js

region_header.js

691 ms

google.fonts.js

google.fonts.js

694 ms

w4theme.behaviors.js

w4theme.behaviors.js

696 ms

w4fancybox.js

w4fancybox.js

697 ms

w4theme.js

w4theme.js

762 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

680 ms

jquery.effects.core.min.js

jquery.effects.core.min.js

607 ms

region_side.js

region_side.js

529 ms

home.js

home.js

531 ms

region_header.css

region_header.css

438 ms

foundation-icons.css

foundation-icons.css

326 ms

w4side.png

w4side.png

90 ms

ecosystem_logo.png

ecosystem_logo.png

92 ms

w4social.png

w4social.png

89 ms

nav_home.png

nav_home.png

88 ms

website.png

website.png

90 ms

nav_training.png

nav_training.png

85 ms

ecosystem.jpg

ecosystem.jpg

170 ms

Network_1.png

Network_1.png

176 ms

Compass_1.png

Compass_1.png

172 ms

HP-Digital-ITESOFT.jpg

HP-Digital-ITESOFT.jpg

520 ms

Digitalisation_1.png

Digitalisation_1.png

120 ms

Setting_2.png

Setting_2.png

121 ms

Interaction_1.png

Interaction_1.png

198 ms

Folder_1.png

Folder_1.png

200 ms

Calendar_1.png

Calendar_1.png

206 ms

Code_1.png

Code_1.png

210 ms

Localisation_1.png

Localisation_1.png

292 ms

ubuntu-v12-latin-regular.woff

ubuntu-v12-latin-regular.woff

283 ms

ubuntu-v12-latin-500.woff

ubuntu-v12-latin-500.woff

366 ms

ubuntu-v12-latin-300.woff

ubuntu-v12-latin-300.woff

487 ms

ubuntu-v12-latin-700.woff

ubuntu-v12-latin-700.woff

383 ms

foundation-icons.woff

foundation-icons.woff

370 ms

Accessibility Review

w4store.com accessibility score

79

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

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

w4store.com best practices score

75

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

SEO Factors

w4store.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

High

robots.txt is not valid

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

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 W4store.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 W4store.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

w4store.com

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