Tools & Wizards About Us
evohe.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

evohe.com

EVOHE, expedition sailing vessel

Page Load Speed

3.1 sec in total

First Response

820 ms

Resources Loaded

2.1 sec

Page Rendered

183 ms

evohe.com screenshot

About Website

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

A 25 metre steel vessel, accommodates 12 passengers on research & natural history filming charters to the New Zealand Subantarctic, Antarctic Peninsula & Pacific Islands

Visit evohe.com

Key Findings

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

evohe.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

evohe.com

820 ms

k2.css

191 ms

rokbox.css

194 ms

menu.css

195 ms

grid-responsive.css

132 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 89% of them (42 requests) were addressed to the original Evohe.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (979 ms) belongs to the original domain Evohe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 792.3 kB (46%)

Content Size

1.7 MB

After Optimization

948.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 17.4 kB

  • Original 22.6 kB
  • After minification 19.4 kB
  • After compression 5.2 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. This page needs HTML code to be minified as it can gain 3.3 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.4 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 10.8 kB

  • Original 680.1 kB
  • After minification 669.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. EVOHE images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 361.2 kB

  • Original 564.6 kB
  • After minification 552.7 kB
  • After compression 203.4 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 361.2 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 402.9 kB

  • Original 473.4 kB
  • After minification 443.9 kB
  • After compression 70.6 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. Evohe.com needs all CSS files to be minified and compressed as it can save up to 402.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (73%)

Requests Now

45

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

evohe.com

evohe.com

820 ms

k2.css

k2.css

191 ms

rokbox.css

rokbox.css

194 ms

menu.css

menu.css

195 ms

grid-responsive.css

grid-responsive.css

132 ms

bootstrap.css

bootstrap.css

319 ms

master-d7f61b1805d119e47f98db4273b3d0c2.css

master-d7f61b1805d119e47f98db4273b3d0c2.css

384 ms

mediaqueries.css

mediaqueries.css

198 ms

thirdparty-k2.css

thirdparty-k2.css

257 ms

css

css

21 ms

rt_metropolis-custom.css

rt_metropolis-custom.css

285 ms

mosaic.css

mosaic.css

290 ms

showcase_responsive.css

showcase_responsive.css

288 ms

style.css

style.css

325 ms

mootools-core.js

mootools-core.js

485 ms

core.js

core.js

372 ms

jquery.min.js

jquery.min.js

8 ms

k2.js

k2.js

372 ms

caption.js

caption.js

403 ms

mootools-more.js

mootools-more.js

521 ms

rokbox.js

rokbox.js

979 ms

browser-engines.js

browser-engines.js

855 ms

rokmediaqueries.js

rokmediaqueries.js

856 ms

rokmediaqueries.js

rokmediaqueries.js

463 ms

responsive.js

responsive.js

554 ms

mootools-mobile.js

mootools-mobile.js

574 ms

rokmediaqueries.js

rokmediaqueries.js

589 ms

roksprocket.js

roksprocket.js

597 ms

moofx.js

moofx.js

642 ms

roksprocket.request.js

roksprocket.request.js

662 ms

mosaic.js

mosaic.js

662 ms

showcase_responsive.js

showcase_responsive.js

709 ms

moofx.js

moofx.js

729 ms

rokmediaqueries.js

rokmediaqueries.js

728 ms

mootools-mobile.js

mootools-mobile.js

776 ms

ga.js

ga.js

80 ms

logo.png

logo.png

271 ms

aeb6d065-9294-4dbb-8c8d-49d8fb872c8a.jpg

aeb6d065-9294-4dbb-8c8d-49d8fb872c8a.jpg

119 ms

7358315b-a430-4b1b-f4e6-36056f35b601.jpg

7358315b-a430-4b1b-f4e6-36056f35b601.jpg

195 ms

a97d1d15-8a91-40bc-9227-66ee4a785bdc.jpg

a97d1d15-8a91-40bc-9227-66ee4a785bdc.jpg

79 ms

914f66a3-b807-41d6-d26a-b21d4610f9f1.jpg

914f66a3-b807-41d6-d26a-b21d4610f9f1.jpg

165 ms

Landing%20at%20Anchorage%20Bay%20Antipode%20Island%20(Photo%20by%20Andrew%20Troup).jpg

Landing%20at%20Anchorage%20Bay%20Antipode%20Island%20(Photo%20by%20Andrew%20Troup).jpg

208 ms

IMG_8951.JPG

IMG_8951.JPG

210 ms

mellish%20081.JPG

mellish%20081.JPG

249 ms

wi-logo.png

wi-logo.png

231 ms

MwQ5bhbm2POE2V9BOA.ttf

MwQ5bhbm2POE2V9BOA.ttf

23 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

evohe.com accessibility score

95

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.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

Links do not have descriptive text

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

evohe.com

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