848 ms in total
37 ms
742 ms
69 ms
Visit localpgh.com now to see the best up-to-date Local Pgh content and also check out these interesting facts you probably never knew about localpgh.com
Local Bar + Kitchen is the South Side's favorite bar & restaurant for drinks with friends, watching the big game, weekend brunch, and more!
Visit localpgh.comWe analyzed Localpgh.com page load time and found that the first response time was 37 ms and then it took 811 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
localpgh.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value6.5 s
9/100
25%
Value5.1 s
62/100
10%
Value1,780 ms
10/100
30%
Value0.062
97/100
15%
Value17.4 s
4/100
10%
37 ms
69 ms
45 ms
49 ms
48 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Localpgh.com, 36% (21 requests) were made to Static.parastorage.com and 29% (17 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (352 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 267.3 kB (29%)
921.6 kB
654.3 kB
In fact, the total size of Localpgh.com main page is 921.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. HTML takes 342.5 kB which makes up the majority of the site volume.
Potential reduce by 262.6 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 262.6 kB or 77% of the original size.
Potential reduce by 1.7 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. Local Pgh 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.
Number of requests can be reduced by 22 (69%)
32
10
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Local Pgh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
localpgh.com
37 ms
www.localbar.com
69 ms
originTrials.41d7301a.bundle.min.js
45 ms
minified.js
49 ms
focus-within-polyfill.js
48 ms
polyfill.min.js
92 ms
inkind.js
91 ms
klaviyo.js
41 ms
thunderbolt-commons.2113c4aa.bundle.min.js
40 ms
main.6c492079.bundle.min.js
81 ms
lodash.min.js
82 ms
react.production.min.js
82 ms
react-dom.production.min.js
141 ms
siteTags.bundle.min.js
138 ms
wix-perf-measure.umd.min.js
139 ms
Local-Bar-%2B-Kitchen-2018.png
253 ms
bundle.min.js
81 ms
807e59_cf19ff2dcd9a4decabc78b948499b60e~mv2_d_5184_3456_s_4_2.jpg
341 ms
807e59_f5e520f45ad64bb3bf67a454bcd5f807~mv2_d_5184_3456_s_4_2.jpg
343 ms
807e59_98f1715ec86445f385bfd10cca1177ba~mv2_d_5184_3456_s_4_2.jpg
352 ms
Local-Bar-%2B-Kitchen-2018.png
206 ms
modal.js
30 ms
fender_analytics.8b21fd7cc915ea15c535.js
90 ms
static.047f24ade89e4aff54a9.js
90 ms
runtime.7d53bcb31ee7ad2422be.js
26 ms
sharedUtils.cb05181f91b3f2ceea9d.js
44 ms
vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js
45 ms
vendors~signup_forms~atlas.de6ae810b114802e47ad.js
40 ms
vendors~signup_forms.8d1bfd5eb9b15cf50941.js
40 ms
signup_forms.5e2fea62c24ac2108007.js
44 ms
132 ms
135 ms
137 ms
133 ms
135 ms
127 ms
180 ms
179 ms
175 ms
174 ms
178 ms
175 ms
221 ms
220 ms
215 ms
199 ms
195 ms
28d74e9b-4ea9-4e3c-b265-c67a72c66856.woff
26 ms
bc176270-17fa-4c78-a343-9fe52824e501.woff
17 ms
07d62b21-8d7a-4c36-be86-d32ab1089972.woff
25 ms
a9e95a29-98a7-404a-90ee-1929ad09c696.woff
25 ms
388ef902-2c31-4818-abb1-a40dcd81f6d6.woff
26 ms
deprecation-en.v5.html
6 ms
bolt-performance
25 ms
deprecation-style.v5.css
8 ms
right-arrow.svg
19 ms
WixMadeforDisplay_W_Bd.woff
6 ms
WixMadeforText_W_Bd.woff
3 ms
WixMadeforText_W_Rg.woff
7 ms
localpgh.com 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
button, link, and menuitem elements do not have accessible names.
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
Buttons do not have an accessible name
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
localpgh.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
Page has valid source maps
localpgh.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Localpgh.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 Localpgh.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.
localpgh.com
Open Graph data is detected on the main page of Local Pgh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: