Tools & Wizards About Us
blueye.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

blueye.com

Blueye - Norwegian Developers of Underwater Technology

Page Load Speed

2 sec in total

First Response

315 ms

Resources Loaded

1.1 sec

Page Rendered

573 ms

blueye.com screenshot

About Website

Visit blueye.com now to see the best up-to-date Blueye content for United States and also check out these interesting facts you probably never knew about blueye.com

Professional underwater ROVs designed, developed, produced, and serviced in Norway. Reliable and user-friendly underwater technology for frictionless access to what's below the surface.

Visit blueye.com

Key Findings

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

Performance Metrics

blueye.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

blueye.com

315 ms

www.blueyerobotics.com

344 ms

gtm.js

80 ms

js

119 ms

css

46 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Blueye.com, 64% (28 requests) were made to Fonts.gstatic.com and 18% (8 requests) were made to Blueyerobotics.com. The less responsive or slowest element that took the longest time to load (484 ms) relates to the external source Js-eu1.hs-scripts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.8 kB (22%)

Content Size

412.0 kB

After Optimization

320.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blueye.com main page is 412.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. 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 159.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 48.1 kB

  • Original 61.3 kB
  • After minification 50.2 kB
  • After compression 13.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 11.1 kB, which is 18% 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 48.1 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 1.5 kB

  • Original 159.1 kB
  • After minification 157.6 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. Blueye images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 33.5 kB

  • Original 153.3 kB
  • After minification 153.3 kB
  • After compression 119.8 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 33.5 kB or 22% of the original size.

CSS Optimization

-23%

Potential reduce by 8.7 kB

  • Original 38.4 kB
  • After minification 38.4 kB
  • After compression 29.7 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. Blueye.com needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (50%)

Requests Now

14

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blueye.com

blueye.com

315 ms

www.blueyerobotics.com

www.blueyerobotics.com

344 ms

gtm.js

gtm.js

80 ms

js

js

119 ms

css

css

46 ms

css2

css2

68 ms

main.css

main.css

102 ms

app.bundle.css

app.bundle.css

154 ms

app.bundle.js

app.bundle.js

449 ms

25227197.js

25227197.js

484 ms

fbevents.js

fbevents.js

46 ms

X3-Front.png

X3-Front.png

67 ms

logo__blueye--white.png

logo__blueye--white.png

157 ms

hero__overlay.png

hero__overlay.png

157 ms

modal__close.png

modal__close.png

223 ms

overlay__close.png

overlay__close.png

236 ms

7cHpv4kjgoGqM7EPCw.ttf

7cHpv4kjgoGqM7EPCw.ttf

56 ms

7cHqv4kjgoGqM7E3_-gc4A.ttf

7cHqv4kjgoGqM7E3_-gc4A.ttf

64 ms

7cHqv4kjgoGqM7E3p-kc4A.ttf

7cHqv4kjgoGqM7E3p-kc4A.ttf

124 ms

7cHqv4kjgoGqM7E3w-oc4A.ttf

7cHqv4kjgoGqM7E3w-oc4A.ttf

181 ms

7cHrv4kjgoGqM7E3b8s8.ttf

7cHrv4kjgoGqM7E3b8s8.ttf

148 ms

7cHqv4kjgoGqM7E30-8c4A.ttf

7cHqv4kjgoGqM7E30-8c4A.ttf

131 ms

7cHqv4kjgoGqM7E3t-4c4A.ttf

7cHqv4kjgoGqM7E3t-4c4A.ttf

147 ms

7cHqv4kjgoGqM7E3q-0c4A.ttf

7cHqv4kjgoGqM7E3q-0c4A.ttf

131 ms

7cHqv4kjgoGqM7E3j-wc4A.ttf

7cHqv4kjgoGqM7E3j-wc4A.ttf

132 ms

HTx3L3I-JCGChYJ8VI-L6OO_au7B2xY.ttf

HTx3L3I-JCGChYJ8VI-L6OO_au7B2xY.ttf

148 ms

HTxwL3I-JCGChYJ8VI-L6OO_au7B4-Lw_3E.ttf

HTxwL3I-JCGChYJ8VI-L6OO_au7B4-Lw_3E.ttf

148 ms

HTxwL3I-JCGChYJ8VI-L6OO_au7B47rx_3E.ttf

HTxwL3I-JCGChYJ8VI-L6OO_au7B47rx_3E.ttf

148 ms

HTxwL3I-JCGChYJ8VI-L6OO_au7B497y_3E.ttf

HTxwL3I-JCGChYJ8VI-L6OO_au7B497y_3E.ttf

151 ms

HTxxL3I-JCGChYJ8VI-L6OO_au7B43LT3w.ttf

HTxxL3I-JCGChYJ8VI-L6OO_au7B43LT3w.ttf

149 ms

HTxwL3I-JCGChYJ8VI-L6OO_au7B4873_3E.ttf

HTxwL3I-JCGChYJ8VI-L6OO_au7B4873_3E.ttf

151 ms

HTxwL3I-JCGChYJ8VI-L6OO_au7B46r2_3E.ttf

HTxwL3I-JCGChYJ8VI-L6OO_au7B46r2_3E.ttf

151 ms

HTxwL3I-JCGChYJ8VI-L6OO_au7B47b1_3E.ttf

HTxwL3I-JCGChYJ8VI-L6OO_au7B47b1_3E.ttf

152 ms

HTxwL3I-JCGChYJ8VI-L6OO_au7B45L0_3E.ttf

HTxwL3I-JCGChYJ8VI-L6OO_au7B45L0_3E.ttf

153 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

151 ms

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrB3XWvA.ttf

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrB3XWvA.ttf

65 ms

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrY3TWvA.ttf

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrY3TWvA.ttf

65 ms

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrf3fWvA.ttf

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrf3fWvA.ttf

64 ms

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrW3bWvA.ttf

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrW3bWvA.ttf

102 ms

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrK3LWvA.ttf

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrK3LWvA.ttf

65 ms

HTxxL3I-JCGChYJ8VI-L6OO_au7B6xTT3w.ttf

HTxxL3I-JCGChYJ8VI-L6OO_au7B6xTT3w.ttf

63 ms

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrc3PWvA.ttf

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrc3PWvA.ttf

73 ms

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrF3DWvA.ttf

HTxyL3I-JCGChYJ8VI-L6OO_au7B6xTrF3DWvA.ttf

95 ms

HTxzL3I-JCGChYJ8VI-L6OO_au7B6xTru1H2.ttf

HTxzL3I-JCGChYJ8VI-L6OO_au7B6xTru1H2.ttf

94 ms

Accessibility Review

blueye.com accessibility score

83

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

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

blueye.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

blueye.com SEO score

90

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

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

blueye.com

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