Tools & Wizards About Us
inevidencecrp.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

inevidencecrp.com

inEvidence | customer storytellers - advocacy / reference specialist

Page Load Speed

2.8 sec in total

First Response

208 ms

Resources Loaded

2.3 sec

Page Rendered

319 ms

inevidencecrp.com screenshot

About Website

Visit inevidencecrp.com now to see the best up-to-date InEvidence Crp content and also check out these interesting facts you probably never knew about inevidencecrp.com

Visit inevidencecrp.com

Key Findings

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

Performance Metrics

inevidencecrp.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value8.7 s

17/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.833

4/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

inevidencecrp.com

208 ms

www.inevidencecrp.com

468 ms

css

36 ms

et-core-unified-13.min.css

87 ms

mediaelementplayer-legacy.min.css

188 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 78% of them (25 requests) were addressed to the original Inevidencecrp.com, 19% (6 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Inevidencecrp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.5 kB (12%)

Content Size

2.4 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 160.6 kB

  • Original 188.0 kB
  • After minification 186.0 kB
  • After compression 27.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 160.6 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 92.5 kB

  • Original 2.0 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. InEvidence Crp images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 31.8 kB

  • Original 188.8 kB
  • After minification 188.8 kB
  • After compression 157.0 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 31.8 kB or 17% of the original size.

CSS Optimization

-13%

Potential reduce by 610 B

  • Original 4.6 kB
  • After minification 4.6 kB
  • After compression 4.0 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. Inevidencecrp.com needs all CSS files to be minified and compressed as it can save up to 610 B or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (48%)

Requests Now

23

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inevidencecrp.com

inevidencecrp.com

208 ms

www.inevidencecrp.com

www.inevidencecrp.com

468 ms

css

css

36 ms

et-core-unified-13.min.css

et-core-unified-13.min.css

87 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

188 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

255 ms

jquery.min.js

jquery.min.js

370 ms

jquery-migrate.min.js

jquery-migrate.min.js

251 ms

scripts.min.js

scripts.min.js

486 ms

magnific-popup.js

magnific-popup.js

287 ms

salvattore.js

salvattore.js

288 ms

common.js

common.js

346 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

471 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

349 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

364 ms

inEvidence_storytellers-BLK-COL-LRG.png

inEvidence_storytellers-BLK-COL-LRG.png

445 ms

our_story.png

our_story.png

468 ms

client_logos_1.png

client_logos_1.png

484 ms

client_logos_2.png

client_logos_2.png

483 ms

client_logos_3.png

client_logos_3.png

554 ms

customer_stories.png

customer_stories.png

571 ms

story_image1.png

story_image1.png

903 ms

story_image2.png

story_image2.png

1007 ms

story_image3.png

story_image3.png

954 ms

preloader.gif

preloader.gif

340 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7j.woff

20 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdo.woff

30 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wmRdo.woff

35 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo.woff

38 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo.woff

46 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdo.woff

40 ms

modules.woff

modules.woff

512 ms

Accessibility Review

inevidencecrp.com accessibility score

80

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

Image elements do not have [alt] attributes

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

inevidencecrp.com 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

inevidencecrp.com SEO score

86

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

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

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

inevidencecrp.com

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