Tools & Wizards About Us
well.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

well.net

The WELL - the birthplace of the online community movement.

Page Load Speed

331 ms in total

First Response

41 ms

Resources Loaded

174 ms

Page Rendered

116 ms

well.net screenshot

About Website

Visit well.net now to see the best up-to-date WELL content and also check out these interesting facts you probably never knew about well.net

Conversation-based community: fascinating people get to know one another at The WELL. The WELL is a primary destination for wide-ranging non-anonymous discussion, online since 1985.

Visit well.net

Key Findings

We analyzed Well.net page load time and found that the first response time was 41 ms and then it took 290 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

well.net performance score

0

Network Requests Diagram

well.net

41 ms

www.well.com

63 ms

well.css

3 ms

vue.css

15 ms

ga.js

16 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 9% of them (1 request) were addressed to the original Well.net, 73% (8 requests) were made to Well.com and 18% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (63 ms) relates to the external source Well.com.

Page Optimization Overview & Recommendations

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

Content Size

72.4 kB

After Optimization

44.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Well.net main page is 72.4 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. Images take 35.9 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.2 kB

  • Original 11.6 kB
  • After minification 9.0 kB
  • After compression 3.4 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 2.7 kB, which is 23% 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 8.2 kB or 71% of the original size.

Image Optimization

-37%

Potential reduce by 13.4 kB

  • Original 35.9 kB
  • After minification 22.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. Obviously, WELL needs image optimization as it can save up to 13.4 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-79%

Potential reduce by 6.1 kB

  • Original 7.7 kB
  • After minification 5.6 kB
  • After compression 1.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. Well.net needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 79% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

well.net

well.net

41 ms

www.well.com

www.well.com

63 ms

well.css

well.css

3 ms

vue.css

vue.css

15 ms

ga.js

ga.js

16 ms

bluelogo144x60.gif

bluelogo144x60.gif

28 ms

bubble_with_yellow.gif

bubble_with_yellow.gif

27 ms

social-twitter-gray-50x50.jpg

social-twitter-gray-50x50.jpg

28 ms

social-gplus-gray-50x50.jpg

social-gplus-gray-50x50.jpg

29 ms

social-FB-50x50.jpg

social-FB-50x50.jpg

29 ms

__utm.gif

__utm.gif

13 ms

SEO Factors

well.net SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Well.net 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 Well.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

well.net

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