80.1 sec in total
212 ms
67.8 sec
12.1 sec
Welcome to oxymoronlist.net homepage info - get ready to check Oxymoron List best content right away, or after learning these important things about oxymoronlist.net
Visit oxymoronlist.netWe analyzed Oxymoronlist.net page load time and found that the first response time was 212 ms and then it took 79.9 sec 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
oxymoronlist.net performance score
name
value
score
weighting
Value17.2 s
0/100
10%
Value18.3 s
0/100
25%
Value24.5 s
0/100
10%
Value2,310 ms
5/100
30%
Value0.004
100/100
15%
Value35.2 s
0/100
10%
212 ms
3289 ms
723 ms
675 ms
676 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Oxymoronlist.net, 17% (30 requests) were made to Oxymoronlist.com and 10% (17 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (22.2 sec) relates to the external source Oxymoronlist.com.
Page size can be reduced by 1.6 MB (51%)
3.1 MB
1.5 MB
In fact, the total size of Oxymoronlist.net main page is 3.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 40.1 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 40.1 kB or 75% of the original size.
Potential reduce by 7.9 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. Oxymoron List images are well optimized though.
Potential reduce by 1.5 MB
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 1.5 MB or 64% of the original size.
Potential reduce by 59.0 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. Oxymoronlist.net needs all CSS files to be minified and compressed as it can save up to 59.0 kB or 82% of the original size.
Number of requests can be reduced by 118 (78%)
151
33
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oxymoron List. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
oxymoronlist.net
212 ms
www.oxymoronlist.com
3289 ms
wp-emoji-release.min.js
723 ms
styles.css
675 ms
css.css
676 ms
usp.css
782 ms
twitter-feed.css
629 ms
css
627 ms
style.css
645 ms
colorbox.css
563 ms
wp-paginate.css
633 ms
jquery.js
680 ms
jquery-migrate.min.js
484 ms
usp-pro.js
485 ms
js.min.js
467 ms
gtm4wp-form-move-tracker.js
430 ms
ios-orientationchange-fix.js
429 ms
jquery.flexslider-min.js
428 ms
jquery.fitvids.js
428 ms
jquery.colorbox-min.js
1237 ms
plusone.js
2499 ms
adsbygoogle.js
395 ms
widgets.js
425 ms
pubcode.min.js
426 ms
jquery.form.min.js
3030 ms
scripts.js
3030 ms
mediaelement-and-player.min.js
3030 ms
wp-mediaelement.min.js
2432 ms
wp-embed.min.js
2987 ms
ga.js
159 ms
__utm.gif
5235 ms
cb=gapi.loaded_0
4692 ms
infinity.js.aspx
2471 ms
header.jpg
2353 ms
search.png
2204 ms
facebook.png
2203 ms
twitter.png
2203 ms
google-plus.png
2203 ms
ca-pub-6391585714755089.js
4260 ms
zrt_lookup.html
4197 ms
show_ads_impl.js
1154 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
2126 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
2524 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
2525 ms
HqHm7BVC_nzzTui2lzQTDSZ2oysoEQEeKwjgmXLRnTc.ttf
2525 ms
lXoKq2PC8Z_S1wl-BwvrB-vvDin1pK8aKteLpeZ5c0A.ttf
2564 ms
y5-5zezrZlJHkmIVxRH3BSZ2oysoEQEeKwjgmXLRnTc.ttf
2516 ms
beacon.js
2916 ms
Tag.engine
5585 ms
pla
1728 ms
ads
498 ms
osd.js
332 ms
xjAJXh38I15wypJXxuGMBiwlidHJgAgmTjOEEzwu1L8.ttf
261 ms
PRmiXeptR36kaC0GEAetxt6Naowg1QhaIq8kLGtQSos.ttf
200 ms
PRmiXeptR36kaC0GEAetxs1QGe9x6ME_FQCWJB3n6z8.ttf
199 ms
b.js
152 ms
cc_af.js
2386 ms
user_sync.html
2455 ms
ads
1129 ms
tpid=73128b317d0340b4b896c042cb989e50
562 ms
sync
638 ms
showad.js
1786 ms
gen_204
1691 ms
ad
1643 ms
m_window_focus_non_hydra.js
6060 ms
osd_listener.js
7503 ms
m_qs_click_protection.js
8440 ms
12-728x90.jpg
10410 ms
abg.js
3578 ms
lidar.js
4494 ms
d5qAyLYU.js
6954 ms
PugMaster
6693 ms
ads
5480 ms
pixel
1963 ms
cookie_push.html
2321 ms
ads
5176 ms
pixel
10084 ms
transparent.png
3031 ms
gen_204
2995 ms
ad
2958 ms
pixel
2994 ms
generic
4979 ms
usersync.aspx
4899 ms
7047 ms
Pug
4258 ms
sync
5030 ms
embed.js
10346 ms
ad
5551 ms
gen_204
5472 ms
pixel
5414 ms
Pug
4815 ms
like.php
8433 ms
9im3l02I.html
3666 ms
demconf.jpg
2268 ms
Pug
3425 ms
get.media
3688 ms
Pug
2618 ms
Pug
2527 ms
Pug
3602 ms
Pug
3454 ms
Pug
3634 ms
Pug
3635 ms
cfcm.ashx
1060 ms
Pug
3086 ms
8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js
1711 ms
Pug
4907 ms
generic
2528 ms
Pug
4940 ms
11-160x600.jpg
7542 ms
pixel
3481 ms
pixel
3564 ms
pixel
3563 ms
Pug
4733 ms
Pug
4722 ms
px
6070 ms
pixel
2698 ms
MFS_Wide_Skyscraper.jpg
2463 ms
receive
2525 ms
LfVJGohmYZB.js
9061 ms
lH1ibRl5GKq.png
9644 ms
8634 ms
user-registering
7435 ms
gtm.js
3043 ms
m
1296 ms
count.js
2376 ms
pixel
4239 ms
sync
6680 ms
lounge.83b5b8f9aa16033ab1cb9cb54bf59140.css
7188 ms
config.js
7187 ms
7399 ms
pixel
4052 ms
admin-ajax.php
22209 ms
button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js
5096 ms
cb=gapi.loaded_1
2329 ms
fastbutton
3525 ms
overlay.png
2574 ms
Pix-1x1.gif
4334 ms
analytics.js
862 ms
postmessageRelay
2526 ms
rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA
1198 ms
collect
989 ms
collect
2441 ms
lounge.load.6f5768194208e9ee5ea7d3e7ec8ac168.js
1223 ms
971028622-postmessagerelay.js
1559 ms
rpc:shindig_random.js
1103 ms
common.bundle.8acee1de90e869efdb244e45c7f66630.js
901 ms
activeview
444 ms
ga-audiences
772 ms
activeview
772 ms
lounge.bundle.9becee0326ce4d1840f8985f1dc0ce21.js
771 ms
common.bundle.8acee1de90e869efdb244e45c7f66630.js
738 ms
tweet_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html
1168 ms
jot
2561 ms
361047.gif
2445 ms
activeview
988 ms
activeview
988 ms
cb=gapi.loaded_0
1098 ms
activeview
212 ms
activeview
523 ms
lounge.83b5b8f9aa16033ab1cb9cb54bf59140.css
184 ms
rt=ifr
685 ms
t
815 ms
5907
458 ms
generic
316 ms
598e4693c55bee4b354eb1948f242ed1
704 ms
image.sbxx
1810 ms
lounge.bundle.9becee0326ce4d1840f8985f1dc0ce21.js
1599 ms
config.js
1355 ms
tpid=6fe49195-8607-49d0-b61b-c4156ba495af
1528 ms
tpid=20b59c6a-1257-49d0-a185-eb2992801249
1757 ms
dptr
1788 ms
tpid=7505428909533393396
1312 ms
tpid=VB69b56f58-9270-11e7-ade9-0e016d72e2ed
1162 ms
tpid=Wa766gAAAQ66-XE@
1289 ms
image.sbxx
1195 ms
tpid=81df2699-1aac-ae9f-f0ff-3aaffd943b3d
5107 ms
oxymoronlist.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
oxymoronlist.net 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
Browser errors were logged to the console
oxymoronlist.net 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 Oxymoronlist.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 Oxymoronlist.net 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.
oxymoronlist.net
Open Graph description is not detected on the main page of Oxymoron List. 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: