Tools & Wizards About Us
ewizard.io screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ewizard.io

Content Experience Platform for Life Sciences and Pharma - eWizard

Page Load Speed

4.6 sec in total

First Response

214 ms

Resources Loaded

3.6 sec

Page Rendered

759 ms

ewizard.io screenshot

About Website

Click here to check amazing EWizard content for Australia. Otherwise, check out these important facts you probably never knew about ewizard.io

Produce content at scale in a multivendor ecosystem using tools, automation, and integrations. Plan campaigns and journeys. Accelerate MLR review.

Visit ewizard.io

Key Findings

We analyzed Ewizard.io page load time and found that the first response time was 214 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

ewizard.io performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

48/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

ewizard.io

214 ms

ewizard.io

1065 ms

5dd5c.js

207 ms

script.js

44 ms

0ec6a.css

375 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 95% of them (80 requests) were addressed to the original Ewizard.io, 2% (2 requests) were made to Webtracking-v01.bpmonline.com and 1% (1 request) were made to Cdn-cookieyes.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ewizard.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 324.8 kB (14%)

Content Size

2.3 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ewizard.io main page is 2.3 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 144.6 kB

  • Original 174.0 kB
  • After minification 174.0 kB
  • After compression 29.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. 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 144.6 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 170.7 kB

  • Original 2.1 MB
  • After minification 1.9 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. EWizard images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 9.4 kB

  • Original 77.7 kB
  • After minification 73.8 kB
  • After compression 68.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 9.4 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (26%)

Requests Now

62

After Optimization

46

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ewizard.io

ewizard.io

214 ms

ewizard.io

ewizard.io

1065 ms

5dd5c.js

5dd5c.js

207 ms

script.js

script.js

44 ms

0ec6a.css

0ec6a.css

375 ms

fd04e.css

fd04e.css

508 ms

jquery.min.js

jquery.min.js

369 ms

ec1b2.css

ec1b2.css

389 ms

1f540.js

1f540.js

486 ms

9934e.js

9934e.js

526 ms

09076.js

09076.js

594 ms

eb631.js

eb631.js

716 ms

track-cookies.js

track-cookies.js

69 ms

create-object.js

create-object.js

70 ms

fa2c4.js

fa2c4.js

611 ms

1615d.js

1615d.js

690 ms

log

log

403 ms

dot_bg_1.svg

dot_bg_1.svg

110 ms

arrow-blue-down.svg

arrow-blue-down.svg

109 ms

checkbox_checked.svg

checkbox_checked.svg

125 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

182 ms

OpenSans-Light.woff

OpenSans-Light.woff

197 ms

OpenSans-SemiBold.woff

OpenSans-SemiBold.woff

196 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

287 ms

OpenSans-ExtraBold.woff

OpenSans-ExtraBold.woff

288 ms

Montserrat-ExtraBold.woff

Montserrat-ExtraBold.woff

307 ms

Montserrat-Bold.woff

Montserrat-Bold.woff

273 ms

Montserrat-Black.woff

Montserrat-Black.woff

288 ms

Montserrat-SemiBold.woff

Montserrat-SemiBold.woff

287 ms

Montserrat-Medium.woff

Montserrat-Medium.woff

366 ms

Montserrat-Regular.woff

Montserrat-Regular.woff

463 ms

Montserrat-Light.woff

Montserrat-Light.woff

377 ms

Montserrat-ExtraLight.woff

Montserrat-ExtraLight.woff

376 ms

Montserrat-Thin.woff

Montserrat-Thin.woff

473 ms

OpenSans-Italic.woff

OpenSans-Italic.woff

398 ms

OpenSans-LightItalic.woff

OpenSans-LightItalic.woff

458 ms

OpenSans-SemiBoldItalic.woff

OpenSans-SemiBoldItalic.woff

474 ms

OpenSans-BoldItalic.woff

OpenSans-BoldItalic.woff

473 ms

OpenSans-ExtraBoldItalic.woff

OpenSans-ExtraBoldItalic.woff

490 ms

logo-horizontal-2.svg

logo-horizontal-2.svg

536 ms

image-40.svg

image-40.svg

902 ms

icons-1-1.svg

icons-1-1.svg

583 ms

icons-4.svg

icons-4.svg

583 ms

icons-2-1.svg

icons-2-1.svg

543 ms

eW_Logo.svg

eW_Logo.svg

584 ms

product-laptop-3-_1_.webp

product-laptop-3-_1_.webp

718 ms

image.png

image.png

727 ms

takeda.svg

takeda.svg

672 ms

teva.svg

teva.svg

674 ms

abbot.svg

abbot.svg

675 ms

santo.svg

santo.svg

800 ms

bayer.svg

bayer.svg

801 ms

biogen-1.svg

biogen-1.svg

802 ms

bayer-Copy.svg

bayer-Copy.svg

822 ms

santo-Copy.svg

santo-Copy.svg

819 ms

abbot-Copy.svg

abbot-Copy.svg

870 ms

teva-Copy.svg

teva-Copy.svg

721 ms

takeda-Copy.svg

takeda-Copy.svg

714 ms

biogen-1-Copy.svg

biogen-1-Copy.svg

861 ms

Library-My-files-1.png

Library-My-files-1.png

797 ms

Frame-535.svg

Frame-535.svg

780 ms

icon-name-7.svg

icon-name-7.svg

781 ms

icon-name-6.svg

icon-name-6.svg

780 ms

icon-name_2.svg

icon-name_2.svg

775 ms

icon-name_3.svg

icon-name_3.svg

762 ms

icon-name-9.svg

icon-name-9.svg

720 ms

icon-name-10.svg

icon-name-10.svg

713 ms

image-4.png

image-4.png

801 ms

ic-bullet-5.svg

ic-bullet-5.svg

697 ms

ic-bullet-1.svg

ic-bullet-1.svg

649 ms

ic-bullet-2.svg

ic-bullet-2.svg

642 ms

ic-bullet-3.svg

ic-bullet-3.svg

706 ms

ic-bullet-4.svg

ic-bullet-4.svg

707 ms

image-23.webp

image-23.webp

711 ms

image-21.webp

image-21.webp

707 ms

image-22.webp

image-22.webp

654 ms

crystal.svg

crystal.svg

712 ms

cloud.svg

cloud.svg

674 ms

rocket.svg

rocket.svg

674 ms

logo-horizontal-1.webp

logo-horizontal-1.webp

678 ms

Frame-3.svg

Frame-3.svg

603 ms

Frame-4.svg

Frame-4.svg

605 ms

Frame-5.svg

Frame-5.svg

671 ms

background-2.svg

background-2.svg

903 ms

Accessibility Review

ewizard.io accessibility score

97

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

ewizard.io best practices score

92

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

SEO Factors

ewizard.io SEO score

92

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 Ewizard.io 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 Ewizard.io 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

ewizard.io

Open Graph data is detected on the main page of EWizard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: