4.1 sec in total
195 ms
1.9 sec
2 sec
Click here to check amazing OGGN content. Otherwise, check out these important facts you probably never knew about oggn.com
The largest, original and most listened to Oil, Gas and Energy podcast network on the planet.
Visit oggn.comWe analyzed Oggn.com page load time and found that the first response time was 195 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
oggn.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value6.5 s
9/100
25%
Value6.3 s
41/100
10%
Value620 ms
48/100
30%
Value0.001
100/100
15%
Value9.0 s
33/100
10%
195 ms
20 ms
208 ms
130 ms
138 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 90% of them (88 requests) were addressed to the original Oggn.com, 3% (3 requests) were made to Stats.wp.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (727 ms) belongs to the original domain Oggn.com.
Page size can be reduced by 182.7 kB (9%)
2.0 MB
1.9 MB
In fact, the total size of Oggn.com main page is 2.0 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 100.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. This page needs HTML code to be minified as it can gain 13.5 kB, which is 11% 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 100.5 kB or 84% of the original size.
Potential reduce by 61.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. OGGN images are well optimized though.
Potential reduce by 3.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.
Potential reduce by 17.8 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. Oggn.com needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 13% of the original size.
Number of requests can be reduced by 64 (69%)
93
29
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OGGN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
oggn.com
195 ms
js
20 ms
style.min.css
208 ms
mediaelementplayer-legacy.min.css
130 ms
wp-mediaelement.min.css
138 ms
settings.css
131 ms
fontello.css
135 ms
css
17 ms
secondline-psb-styles.css
204 ms
woocommerce-layout.css
219 ms
woocommerce.css
212 ms
wp-post-modal-public.css
218 ms
frontend.min.css
223 ms
all.min.css
228 ms
slick.css
240 ms
160e4b57041ce4a259363983eaae1c4e.css
293 ms
style.css
299 ms
main.css
338 ms
loader.css
295 ms
responsive.css
354 ms
formreset.min.css
330 ms
formsmain.min.css
380 ms
readyclass.min.css
393 ms
browsers.min.css
408 ms
wp-polyfill-inert.min.js
489 ms
regenerator-runtime.min.js
354 ms
wp-polyfill.min.js
476 ms
hooks.min.js
453 ms
w.js
32 ms
frontend-gtag.min.js
474 ms
jquery.min.js
531 ms
jquery-migrate.min.js
508 ms
jquery.blockUI.min.js
547 ms
add-to-cart.min.js
570 ms
js.cookie.min.js
581 ms
woocommerce.min.js
673 ms
wp-post-modal-public.js
612 ms
s-202410.js
31 ms
jquery.json.min.js
663 ms
gravityforms.min.js
675 ms
api.js
51 ms
js
71 ms
e-202410.js
7 ms
utils.min.js
639 ms
modal.min.js
469 ms
sourcebuster.min.js
570 ms
order-attribution.min.js
574 ms
underscore.min.js
524 ms
wp-util.min.js
525 ms
api-request.min.js
565 ms
i18n.min.js
562 ms
url.min.js
592 ms
api-fetch.min.js
588 ms
frontend.min.js
613 ms
slick.min.js
600 ms
jquery.marquee.min.js
555 ms
navigation.js
586 ms
jquery.cookie.min.js
605 ms
theme.js
605 ms
jquery.waypoint.min.js
589 ms
dom-ready.min.js
566 ms
a11y.min.js
576 ms
jquery.textareaCounter.plugin.min.js
654 ms
placeholders.jquery.min.js
626 ms
vendor-theme.min.js
617 ms
scripts-theme.min.js
605 ms
g.gif
4 ms
oggn-white-600.png
212 ms
ogtw-web-1-300x300.jpg
251 ms
cifk-web-300x300.jpg
241 ms
ogu-web-300x300.jpg
244 ms
hse-web-300x300.jpg
236 ms
ets-web-300x300.jpg
243 ms
esg-web-300x300.jpg
266 ms
ben-web.jpg
250 ms
fsu-web.jpg
459 ms
pitch-web.jpg
458 ms
b3e-web.jpg
470 ms
ogdd-web-1.jpg
438 ms
fa-brands-400.woff
423 ms
fa-regular-400.woff
388 ms
fa-solid-900.woff
495 ms
ogil-web.jpg
442 ms
ogsm-web.jpg
410 ms
tbp-web.jpg
585 ms
ewt-web.jpg
610 ms
mixc-web.jpg
538 ms
tep-web-1.jpg
578 ms
oi-web-300x300.jpg
514 ms
tef-web-300x300.jpg
512 ms
pp-web-300x300.jpg
691 ms
jecs-web-300x300.jpg
678 ms
esu-web-300x300.jpg
654 ms
oglr-web-297x300.png
727 ms
ogof-web-300x300.png
716 ms
g.gif
22 ms
recaptcha__en.js
26 ms
woocommerce-smallscreen.css
95 ms
oggn.com accessibility score
Names and labels
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.
Impact
Issue
Form elements do not have associated labels
Links do not have a discernible name
oggn.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
oggn.com SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oggn.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 Oggn.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.
oggn.com
Open Graph data is detected on the main page of OGGN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: