Tools & Wizards About Us
headwave.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

headwave.com

Subsurface Data Cloud & Interpretation Solutions | Bluware

Page Load Speed

1.2 sec in total

First Response

310 ms

Resources Loaded

672 ms

Page Rendered

169 ms

headwave.com screenshot

About Website

Click here to check amazing Headwave content. Otherwise, check out these important facts you probably never knew about headwave.com

Maximize subsurface data value with seismic deep learning to reduce interpretation cycle time. Increase efficiency with cloud storage, save time, and cut costs.

Visit headwave.com

Key Findings

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

Performance Metrics

headwave.com performance score

0

Network Requests Diagram

headwave.com

310 ms

css

26 ms

system.base.css

11 ms

system.messages.css

11 ms

simplenews.css

11 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 79% of them (30 requests) were addressed to the original Headwave.com, 13% (5 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (310 ms) belongs to the original domain Headwave.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 672.8 kB (38%)

Content Size

1.8 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 13.0 kB

  • Original 17.5 kB
  • After minification 16.5 kB
  • After compression 4.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 13.0 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 50.0 kB

  • Original 973.4 kB
  • After minification 923.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. Headwave images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 313.9 kB

  • Original 426.4 kB
  • After minification 308.4 kB
  • After compression 112.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 313.9 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 295.9 kB

  • Original 345.0 kB
  • After minification 275.9 kB
  • After compression 49.1 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. Headwave.com needs all CSS files to be minified and compressed as it can save up to 295.9 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

headwave.com

headwave.com

310 ms

css

css

26 ms

system.base.css

system.base.css

11 ms

system.messages.css

system.messages.css

11 ms

simplenews.css

simplenews.css

11 ms

comment.css

comment.css

12 ms

date.css

date.css

11 ms

datepicker.1.7.css

datepicker.1.7.css

10 ms

field.css

field.css

10 ms

node.css

node.css

11 ms

search.css

search.css

11 ms

user.css

user.css

9 ms

views.css

views.css

11 ms

ctools.css

ctools.css

14 ms

entypo-icon-font.css

entypo-icon-font.css

10 ms

bootstrap.css

bootstrap.css

158 ms

template.min.css

template.min.css

144 ms

slider.css

slider.css

46 ms

color.css

color.css

47 ms

custom.css

custom.css

165 ms

bigwig_sub.css

bigwig_sub.css

47 ms

jquery.min.js

jquery.min.js

180 ms

jquery.once.js

jquery.once.js

53 ms

drupal.js

drupal.js

54 ms

googleanalytics.js

googleanalytics.js

55 ms

template.min.js

template.min.js

229 ms

bigwig.js

bigwig.js

59 ms

bootstrap.min.js

bootstrap.min.js

89 ms

analytics.js

analytics.js

5 ms

collect

collect

90 ms

2015_Headwave_logo_website_data_driven.png

2015_Headwave_logo_website_data_driven.png

4 ms

2016_Homeslider_Pic.jpg

2016_Homeslider_Pic.jpg

45 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

9 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

14 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

41 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

40 ms

entypo-icon-font.woff

entypo-icon-font.woff

13 ms

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

40 ms

SEO Factors

headwave.com SEO score

0

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

headwave.com

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