4.5 sec in total
882 ms
2.7 sec
903 ms
Welcome to onionpub.com homepage info - get ready to check Onion Pub best content for United States right away, or after learning these important things about onionpub.com
Visit onionpub.comWe analyzed Onionpub.com page load time and found that the first response time was 882 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
onionpub.com performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value12.2 s
0/100
25%
Value12.8 s
2/100
10%
Value1,030 ms
26/100
30%
Value0.001
100/100
15%
Value14.0 s
10/100
10%
882 ms
22 ms
17 ms
27 ms
40 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Onionpub.com, 5% (6 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (882 ms) relates to the external source Onionbrewery.com.
Page size can be reduced by 1.1 MB (19%)
5.9 MB
4.8 MB
In fact, the total size of Onionpub.com main page is 5.9 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. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 86.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 86.1 kB or 83% of the original size.
Potential reduce by 377 B
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. Onion Pub images are well optimized though.
Potential reduce by 439.2 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 439.2 kB or 60% of the original size.
Potential reduce by 597.1 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. Onionpub.com needs all CSS files to be minified and compressed as it can save up to 597.1 kB or 75% of the original size.
Number of requests can be reduced by 80 (78%)
103
23
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Onion Pub. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
onionbrewery.com
882 ms
wp-emoji-release.min.js
22 ms
03763c63dc26eee321c26a0c0d5c03b5.css
17 ms
909ad171974489e450cd5c92d7267c0e.css
27 ms
48817d8bd1df01bc1ec659fbc84df8d3.css
40 ms
font-awesome.min.css
45 ms
animate.css
60 ms
slick.css
33 ms
loaders.css
94 ms
priority-nav-core.css
38 ms
hover.css
74 ms
pagination.css
66 ms
jquery.mCustomScrollbar.min.css
78 ms
common-skeleton.min.css
89 ms
tooltip.min.css
77 ms
style.min.css
83 ms
theme.min.css
91 ms
settings.css
109 ms
bootstrap.css
147 ms
flexslider.min.css
139 ms
shortcodes.css
143 ms
animate.min.css
183 ms
style.css
202 ms
bootstrap-responsive.css
178 ms
jquery.fancybox.css
185 ms
vector-icons.css
189 ms
font-awesome.min.css
196 ms
linecon.css
195 ms
steadysets.css
193 ms
hoverex-all.css
214 ms
jquery.easy-pie-chart.css
219 ms
idangerous.swiper.css
221 ms
js_composer.min.css
256 ms
ubermenu.min.css
219 ms
font-awesome.min.css
221 ms
css
71 ms
core.css
229 ms
css
70 ms
js
213 ms
vc_openiconic.min.css
220 ms
lazysizes.js
218 ms
jquery.js
215 ms
jquery-migrate.min.js
208 ms
jquery.themepunch.tools.min.js
266 ms
jquery.themepunch.revolution.min.js
265 ms
post-like.js
220 ms
bootstrap.min.js
193 ms
jquery.easing.1.1.js
231 ms
jquery.easing.1.3.js
235 ms
jquery.mobilemenu.js
228 ms
isotope.js
225 ms
jquery.flexslider-min.js
214 ms
jquery.fancybox.js
211 ms
jquery.fancybox-media.js
213 ms
jquery.carouFredSel-6.1.0-packed.js
196 ms
jquery.hoverex.js
189 ms
tooltip.js
163 ms
jquery.parallax.js
161 ms
modernizr.custom.66803.js
135 ms
jquery.appear.js
124 ms
jquery.easy-pie-chart.js
121 ms
odometer.min.js
120 ms
animations.js
120 ms
main.js
112 ms
jquery.placeholder.min.js
111 ms
jquery.countdown.min.js
109 ms
waypoints.min.js
94 ms
idangerous.swiper.min.js
93 ms
background-check.min.js
91 ms
jquery.fullPage.js
89 ms
skrollr.min.js
91 ms
select2.min.js
90 ms
jquery.slicknav.min.js
89 ms
classie.js
89 ms
jquery.mixitup.js
88 ms
imagesloaded.min.js
88 ms
css
88 ms
masonry.min.js
144 ms
jquery.onepage.js
134 ms
jquery.infinitescroll.min.js
133 ms
ubermenu.min.js
98 ms
wp-embed.min.js
96 ms
js_composer_front.min.js
96 ms
ob-logo.png
25 ms
BT7B0105.jpg
127 ms
BT7B1319.jpg
128 ms
BT7B0076.jpg
121 ms
BT7B0257.jpg
132 ms
BT7B0270.jpg
130 ms
cans_home.jpg
130 ms
footer2.jpg
140 ms
back6-1.jpg
138 ms
back7.jpg
157 ms
banquet5__900W.jpg
140 ms
icon_top.png
139 ms
revolution.extension.slideanims.min.js
84 ms
revolution.extension.actions.min.js
86 ms
revolution.extension.layeranimation.min.js
89 ms
revolution.extension.kenburn.min.js
85 ms
revolution.extension.parallax.min.js
85 ms
mem5YaGs126MiZpBA-UNirkOUuhs.ttf
123 ms
mem5YaGs126MiZpBA-UN7rgOUuhs.ttf
138 ms
mem5YaGs126MiZpBA-UN8rsOUuhs.ttf
139 ms
mem8YaGs126MiZpBA-UFVZ0e.ttf
139 ms
mem5YaGs126MiZpBA-UN_r8OUuhs.ttf
138 ms
fontawesome-webfont.woff
95 ms
fontawesome-webfont.woff
83 ms
fontawesome-webfont.woff
110 ms
qWcqB6WkuIDxDZLcPrxeuA.ttf
98 ms
vc_openiconic.woff
83 ms
onionpub.com accessibility score
onionpub.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
onionpub.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Onionpub.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 Onionpub.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.
onionpub.com
Open Graph description is not detected on the main page of Onion Pub. 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: