Tools & Wizards About Us
myevive.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

myevive.com

MyEvive

Page Load Speed

1.5 sec in total

First Response

102 ms

Resources Loaded

1.2 sec

Page Rendered

150 ms

myevive.com screenshot

About Website

Welcome to myevive.com homepage info - get ready to check My Evive best content for United States right away, or after learning these important things about myevive.com

MyEvive Multi public page

Visit myevive.com

Key Findings

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

Performance Metrics

myevive.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.836

4/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

myevive.com

102 ms

myevive.com

257 ms

foundation_index.min.css

437 ms

foundation-icons-5.3.0.min.css

480 ms

myevive.min.css

206 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 38% of them (3 requests) were addressed to the original Myevive.com, 38% (3 requests) were made to 047f018102c8c8f717a6-1efb167bc857a9871c34d9fa1ea1cbde.ssl.cf1.rackcdn.com and 25% (2 requests) were made to A69eb76f577bcd91cb7c-dfbe26a5a69f508d9139ebbbd82f60c6.ssl.cf1.rackcdn.com. The less responsive or slowest element that took the longest time to load (480 ms) relates to the external source 047f018102c8c8f717a6-1efb167bc857a9871c34d9fa1ea1cbde.ssl.cf1.rackcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.1 kB (72%)

Content Size

165.0 kB

After Optimization

46.8 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Myevive.com main page is 165.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. Only 10% of websites need less resources to load. CSS take 134.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 4.3 kB

  • Original 5.8 kB
  • After minification 5.6 kB
  • After compression 1.6 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 4.3 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 24.5 kB
  • After minification 24.5 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. My Evive images are well optimized though.

CSS Optimization

-85%

Potential reduce by 113.9 kB

  • Original 134.7 kB
  • After minification 134.6 kB
  • After compression 20.8 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. Myevive.com needs all CSS files to be minified and compressed as it can save up to 113.9 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • CSS

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Evive. According to our analytics all requests are already optimized.

Network Requests Diagram

myevive.com

myevive.com

102 ms

myevive.com

myevive.com

257 ms

foundation_index.min.css

foundation_index.min.css

437 ms

foundation-icons-5.3.0.min.css

foundation-icons-5.3.0.min.css

480 ms

myevive.min.css

myevive.min.css

206 ms

myevive_white.png

myevive_white.png

108 ms

ev-phone.jpg

ev-phone.jpg

223 ms

foundation-icons.woff

foundation-icons.woff

349 ms

Accessibility Review

myevive.com accessibility score

100

Accessibility Issues

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

myevive.com SEO score

100

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myevive.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Myevive.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

myevive.com

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