ogj.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

33 files are served with short cache lifetimes, so returning visitors download them again (986 KiB).

Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 6.3 s on main-thread work while loading, 4.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Audience 360 and Google/Doubleclick Ads and others), adding 2.6 MB and 1.7 s of main-thread time.

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

Google Tag Manager costs a phone 427 ms of main-thread work and 799 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google/Doubleclick Ads costs a phone 311 ms of main-thread work and 581 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

19 long tasks block the main thread while loading, the longest for 357 ms. During a long task the page ignores taps.

Audience 360 costs a phone 315 ms of main-thread work and 26 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

transcend-cdn.com costs a phone 267 ms of main-thread work and 135 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 1,686 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

podbean.com costs a phone 114 ms of main-thread work and 541 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

8 images could be 179 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

About 16 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

Polyfills for old browsers add 42 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Grey map with the Gulf of Mexico, the South Atlantic Margin…”.

The page becomes fully interactive after 27.4 s. Good is under 3.8 s.

Visually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 996 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 210 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

The layout shifts by 0.206 while loading, so content jumps under the reader's thumb. Good is under 0.1.

The first text or image appears after 2.2 s on a phone. Good is under 1.8 s.

4 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 143 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.5 MB in 303 requests on a phone: scripts 2.9 MB (120), images 776 KiB (40) and other files 725 KiB (117). Under 2 MB keeps phones on slow connections fast.

6ae4de8ebb6ffc3e8b661b9b-cvx_exploration_map_2026_10.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images (169 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (140 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 154.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

68 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements must only use permitted ARIA attributes: 8 elements on the page fail this check, rated serious by axe-core.

4 tap targets are too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 24 characters: “Home | Oil & Gas Journal”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 9 <h1> headlines (“Trending”, “Members Only” and “Learning Resources”). One clear main headline is easier for people and search engines.

Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (NewsMediaOrganization and WebSite) but with 2 problems, for example “NewsMediaOrganization: sameAs is an empty list”.

2 links have no real href, so search engines can't follow them.

The homepage links to 143 pages on ogj.com and 24 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.ogj.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.ogj.com/podcasts and https://www.ogj.com/magazine declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://www.ogj.com/members, https://www.ogj.com/podcasts and https://www.ogj.com/magazine have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.

15 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,781 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 31 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.