21.1 sec in total
312 ms
20.4 sec
474 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 312 ms and then it took 20.8 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.
guinness.pl performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value11.0 s
0/100
25%
Value5.1 s
62/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value13.0 s
13/100
10%
312 ms
111 ms
121 ms
121 ms
46 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 77% of them (33 requests) were addressed to the original Guinness.pl, 5% (2 requests) were made to Connect.facebook.net and 5% (2 requests) were made to Tripadvisor.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Tripadvisor.com.
Page size can be reduced by 22.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. 75% 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.0 MB which makes up the majority of the site volume.
Potential reduce by 20.7 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. This page needs HTML code to be minified as it can gain 3.0 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 20.7 kB or 76% of the original size.
Potential reduce by 1.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. Guinness images are well optimized though.
Potential reduce by 286 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 23 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 6 (17%)
35
29
The browser has sent 35 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 7 to 1 for JavaScripts and as a result speed up the page load time.
guinness.pl
312 ms
en
111 ms
121 ms
A.style.css,qv=12.pagespeed.cf.jTMpaksw-a.css
121 ms
css
46 ms
xlogowhite3.png.pagespeed.ic.OxEYzIfcsI.png
154 ms
s0.jpg
45 ms
s0b.jpg
30 ms
s1.jpg
31 ms
s2.jpg
31 ms
s3.jpg
45 ms
s4.jpg
45 ms
instawidget.js
174 ms
lightbox.min.css
41 ms
jquery-3.1.1.min.js
55 ms
jquery.bxslider.min.js
54 ms
jquery.inview.js
54 ms
javascript.js
54 ms
js
121 ms
languages.png
5 ms
bar-bgn.jpg
8 ms
kitchen-bgn.jpg
7 ms
arrow-box.png
5 ms
steak-bgn.jpg
14 ms
xbbq-bgn.jpg.pagespeed.ic.8sEBlPmPIw.jpg
260 ms
oferta-bgn3.jpg
20 ms
social-bg.jpg
21 ms
xirish-tarcza.jpg.pagespeed.ic.1cJGLMwTd5.jpg
155 ms
sdk.js
18 ms
xfooter-bg.jpg.pagespeed.ic.smfJl9ccx4.jpg
111 ms
fb.png
6 ms
tripadvisor.png
8 ms
close.png
110 ms
loading.gif
115 ms
prev.png
117 ms
next.png
202 ms
sdk.js
5 ms
59 ms
wejs
19560 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
45 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
69 ms
DroidSerif-Regular.ttf
15 ms
150_logo-11900-2.png
56 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: