Access wtrg.com. WTRG Economics -OPEC, crude oil, natural gas, analysis, forecasts and data

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.1 s

76/100

10%

wtrg.com

208 ms

show_ads.js

69 ms

WTRG.gif

61 ms

punit1.gif

178 ms

adsbygoogle.js

108 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 60% of them (3 requests) were addressed to the original Wtrg.com, 40% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (208 ms) belongs to the original domain Wtrg.com.

Content Size

134.7 kB

After Optimization

85.7 kB

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

HTML Optimization

-87%

Potential reduce by 49.0 kB

Original 56.6 kB
After minification 26.1 kB
After compression 7.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. This page needs HTML code to be minified as it can gain 30.5 kB, which is 54% 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 49.0 kB or 87% of the original size.

JavaScript Optimization

-0%

Potential reduce by 39 B

Original 78.1 kB
After minification 78.1 kB
After compression 78.0 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.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Image elements do not have [alt] attributes

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wtrg.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wtrg.com main page’s claimed encoding is windows-1252. 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

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