2.8 sec in total
434 ms
2 sec
349 ms
Welcome to guinness.pl homepage info - get ready to check Guinness best content right away, or after learning these important things about guinness.pl
Irish Pub to kultowy lokal w Rzeszowie. Osiem różniących się od siebie klimatem sal, Największy wybór whisky, doskonałe jedzenie i niepowtarzalny klimat.
Visit guinness.plWe analyzed Guinness.pl page load time and found that the first response time was 434 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
guinness.pl performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value6.2 s
11/100
25%
Value6.5 s
39/100
10%
Value100 ms
98/100
30%
Value1.025
2/100
15%
Value15.5 s
7/100
10%
434 ms
115 ms
135 ms
147 ms
38 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 64% of them (30 requests) were addressed to the original Guinness.pl, 9% (4 requests) were made to Tripadvisor.com and 6% (3 requests) were made to Static.tacdn.com. The less responsive or slowest element that took the longest time to load (983 ms) belongs to the original domain Guinness.pl.
Page size can be reduced by 29.3 kB (1%)
4.1 MB
4.1 MB
In fact, the total size of Guinness.pl main page is 4.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. 40% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 27.8 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 27.8 kB or 74% of the original size.
Potential reduce by 1.2 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. Guinness images are well optimized though.
Potential reduce by 243 B
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 20 B
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. Guinness.pl has all CSS files already compressed.
Number of requests can be reduced by 13 (33%)
39
26
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guinness. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
guinness.pl
434 ms
en
115 ms
135 ms
A.style.css,qv=12.pagespeed.cf.cgWtoN-927.css
147 ms
css
38 ms
instawidget.js
91 ms
lightbox.min.css
234 ms
jquery-3.1.1.min.js
234 ms
jquery.bxslider.min.js
246 ms
jquery.inview.js
313 ms
javascript.js
319 ms
js
152 ms
wejs
36 ms
xlogowhite3.png.pagespeed.ic.OxEYzIfcsI.png
215 ms
languages.png
248 ms
s0.jpg
584 ms
s0b.jpg
580 ms
s1.jpg
635 ms
s2.jpg
540 ms
s3.jpg
690 ms
s4.jpg
572 ms
bar-bgn.jpg
820 ms
kitchen-bgn.jpg
793 ms
steak-bgn.jpg
889 ms
xbbq-bgn.jpg.pagespeed.ic.8sEBlPmPIw.jpg
777 ms
oferta-bgn3.jpg
842 ms
social-bg.jpg
851 ms
xfooter-bg.jpg.pagespeed.ic.smfJl9ccx4.jpg
941 ms
xirish-tarcza.jpg.pagespeed.ic.1cJGLMwTd5.jpg
965 ms
150_logo-11900-2.png
17 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
22 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
22 ms
DroidSerif-Regular.ttf
926 ms
sdk.js
19 ms
WidgetEmbed-selfserveprop
43 ms
close.png
945 ms
loading.gif
944 ms
prev.png
948 ms
next.png
983 ms
sdk.js
6 ms
52 ms
t4b_widget_self_serve_property-v24221562771a.css
19 ms
cdswidgets_m-c-v22480917520a.js
22 ms
Tripadvisor_lockup_horizontal_secondary_registered-11900-2.svg
65 ms
page.php
72 ms
TripAdvisor_Regular.woff
4 ms
bTjav475CFJ.css
15 ms
guinness.pl 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
Buttons do not have an accessible name
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
guinness.pl 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
Browser errors were logged to the console
guinness.pl 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guinness.pl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Guinness.pl 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.
guinness.pl
Open Graph data is detected on the main page of Guinness. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: