6.2 sec in total
1.8 sec
3.4 sec
1 sec
Welcome to primobar.net homepage info - get ready to check Primo Bar best content right away, or after learning these important things about primobar.net
Elevate Your Event with Mobile Bartending & Beverage Catering by Primo Bar! Customized service, pro event staff and rentals for events throughout Northern CA.
Visit primobar.netWe analyzed Primobar.net page load time and found that the first response time was 1.8 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
primobar.net performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value10.3 s
0/100
25%
Value6.0 s
46/100
10%
Value260 ms
83/100
30%
Value0.121
84/100
15%
Value11.0 s
21/100
10%
1820 ms
23 ms
195 ms
16 ms
185 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 76% of them (86 requests) were addressed to the original Primobar.net, 19% (21 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Primobar.net.
Page size can be reduced by 299.3 kB (11%)
2.8 MB
2.5 MB
In fact, the total size of Primobar.net main page is 2.8 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. 80% 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 67.2 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 67.2 kB or 80% of the original size.
Potential reduce by 58.3 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. Primo Bar images are well optimized though.
Potential reduce by 33.4 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 33.4 kB or 21% of the original size.
Potential reduce by 140.3 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. Primobar.net needs all CSS files to be minified and compressed as it can save up to 140.3 kB or 47% of the original size.
Number of requests can be reduced by 49 (55%)
89
40
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Primo Bar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
primobar.net
1820 ms
analytics.js
23 ms
styles.css
195 ms
jquery-ui.min.css
16 ms
jquery-ui-timepicker-addon.min.css
185 ms
primobar.net
233 ms
kingcomposer.min.css
195 ms
animate.css
190 ms
icons.css
185 ms
owl.theme.css
201 ms
owl.carousel.css
211 ms
reset.css
212 ms
bootstrap.min.css
220 ms
style.css
261 ms
icons.css
265 ms
animate.css
275 ms
highstand.css
450 ms
ms-slider.css
283 ms
external.css
294 ms
shortcodes.css
384 ms
slidebars.css
327 ms
css
35 ms
menu-8.css
338 ms
responsive.css
411 ms
jquery.js
426 ms
jquery-migrate.min.js
393 ms
highstand.user.js
403 ms
css
48 ms
collect
16 ms
post-like.js
527 ms
scripts.js
528 ms
core.min.js
528 ms
datepicker.min.js
529 ms
jquery-ui-timepicker-addon.min.js
530 ms
widget.min.js
531 ms
mouse.min.js
531 ms
slider.min.js
531 ms
button.min.js
532 ms
jquery-ui-sliderAccess.js
533 ms
blankshield.min.js
534 ms
block-tabnapping.js
572 ms
js
61 ms
scroll-to-anchor.min.js
570 ms
kingcomposer.min.js
438 ms
owl.carousel.min.js
444 ms
slidebars.js
446 ms
custom.js
447 ms
highstand.user.js
505 ms
viewportchecker.js
502 ms
custom.js
493 ms
comment-reply.min.js
492 ms
wp-embed.min.js
481 ms
shortcode.js
477 ms
header-logo-432.png
293 ms
maintenance-bg.jpg
312 ms
elevate.png
293 ms
your-event-1.png
294 ms
primo-bar-logo.png
338 ms
drinks-on-blk-flat-2.jpg
338 ms
beer1.jpg
438 ms
700px-wide-1.jpg
458 ms
aha-300x199.png
341 ms
ameriprise-300x199.png
375 ms
cda-300x199.png
404 ms
calpers-300x199.png
407 ms
elkgrove-300x199.png
355 ms
fredericks-300x199.png
385 ms
intel-300x199.png
417 ms
k1speed-300x199.png
418 ms
airport-300x199.png
413 ms
sailor-jerry-300x199.png
446 ms
sutter-300x199.png
451 ms
toll-bros-300x199.png
472 ms
ucdavis-300x199.png
473 ms
westsac-300x199.png
478 ms
xopjet-300x199.png
478 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
40 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
41 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
42 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
45 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
44 ms
zOL64pLDlL1D99S8g8PtiKchq-dmiA.ttf
44 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
44 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
45 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
46 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
50 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
49 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
46 ms
9573.jpg
512 ms
beer-wide.jpg
496 ms
services-side-title-1.jpg
494 ms
spacer-image-1.jpg
558 ms
spacer-image-2.jpg
492 ms
champagne-wide.jpg
547 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
59 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
61 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf
62 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
60 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
61 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
60 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
62 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf
62 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf
63 ms
fontawesome-webfont.woff
526 ms
fa-solid-900.woff
495 ms
champagne4.jpg
482 ms
wendy-no-logo-420x302xc.jpg
493 ms
primo-bar-logo-300x181.png
524 ms
elevate-footer-800.png
432 ms
elevate-footer-2.png
433 ms
scroll-top-arrow.png
439 ms
ajax-loader.gif
437 ms
drinks-on-blk2.jpg
69 ms
primobar.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
primobar.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
primobar.net 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Primobar.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 Primobar.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.
primobar.net
Open Graph data is detected on the main page of Primo Bar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: