2.8 sec in total
358 ms
1.9 sec
508 ms
Click here to check amazing Dublin content for Ireland. Otherwise, check out these important facts you probably never knew about dublin.pub
Visit dublin.pubWe analyzed Dublin.pub page load time and found that the first response time was 358 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.
dublin.pub performance score
358 ms
22 ms
71 ms
273 ms
42 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Dublin.pub, 28% (44 requests) were made to Maps.googleapis.com and 25% (40 requests) were made to D35onr1h4eb0bw.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source D35onr1h4eb0bw.cloudfront.net.
Page size can be reduced by 966.7 kB (51%)
1.9 MB
933.1 kB
In fact, the total size of Dublin.pub main page is 1.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. 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 172.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 172.1 kB or 87% of the original size.
Potential reduce by 19.5 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. Dublin images are well optimized though.
Potential reduce by 775.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 775.0 kB or 69% of the original size.
Number of requests can be reduced by 33 (22%)
148
115
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dublin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.
dublin.pub
358 ms
jquery.min.js
22 ms
js
71 ms
infobubble.js
273 ms
css
42 ms
site_290544_79129_110.css
451 ms
filter-UI.js
243 ms
published-site-jquery-lightbox.js
10 ms
translations.js
8 ms
published-site.js
23 ms
twig-widget-views-v2.js
9 ms
navigation.js
179 ms
ga.js
18 ms
logo-name.png
297 ms
pub-logo-mc-daids.svg
91 ms
pub-photo-mc-daids.jpg
339 ms
pub-logo-the-long-hall.svg
91 ms
pub-photo-the-long-hall.jpg
402 ms
pub-logo-davy-byrnes.svg
294 ms
pub-photo-davy-byrnes.jpg
338 ms
pub-logo-john-kehoe.svg
364 ms
pub-photo-john-kehoe.jpg
742 ms
pub-logo-doheny-nesbitt.svg
460 ms
pub-photo-doheny-nesbitt.jpg
494 ms
pub-logo-toners.svg
432 ms
pub-photo-toners.jpg
537 ms
pub-logo-nearys.svg
509 ms
pub-photo-nearys.jpg
710 ms
pub-logo-the-international-bar.svg
530 ms
pub-photo-the-international-bar.jpg
917 ms
pub-logo-the-stags-head.svg
582 ms
pub-photo-the-stags-head.jpg
829 ms
pub-logo-the-ferryman.svg
844 ms
pub-photo-the-ferryman.jpg
816 ms
pub-logo-the-hairy-lemon.svg
791 ms
pub-photo-the-hairy-lemon.jpg
1123 ms
pub-logo-mv-cill-airne.svg
872 ms
pub-photo-mv-cill-airne.jpg
899 ms
pub-logo-odonoghues-bar.svg
909 ms
pub-photo-odonoghues-bar.jpg
1090 ms
pub-logo-crowes.svg
952 ms
pub-photo-crowes.jpg
1056 ms
logo-basekit.svg
990 ms
logo-tapastreet.png
993 ms
sdk.js
55 ms
widgets.js
89 ms
__utm.gif
23 ms
feature2.jpg
1127 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
19 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
20 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
20 ms
fontawesome-webfont.woff
18 ms
274 ms
common.js
175 ms
map.js
227 ms
util.js
254 ms
geometry.js
196 ms
directions.js
252 ms
undefined
257 ms
overlay.js
192 ms
mcdaids1.jpg
392 ms
iw_close.gif
249 ms
marker.js
211 ms
10881984_1608757022686301_958410228_n.jpg
294 ms
xd_arbiter.php
76 ms
xd_arbiter.php
131 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
205 ms
11352937_437282376443152_912651796_n.jpg
109 ms
1515386_1429703120597674_1107532594_n.jpg
112 ms
mcdaids2.jpg
361 ms
mcdaids3.jpg
288 ms
longhall1.jpg
446 ms
longhall2.jpg
486 ms
longhall3.jpg
298 ms
davybyrnes1.jpg
360 ms
davybyrnes2.jpg
414 ms
davybyrnes3.jpg
385 ms
johnkehoe1.jpg
446 ms
johnkehoe2.jpg
445 ms
johnkehoe3.jpg
475 ms
dohenynesbitt1.jpg
568 ms
dohenynesbitt2.jpg
594 ms
dohenynesbitt3.jpg
518 ms
toners1.jpg
522 ms
toners2.jpg
547 ms
toners3.jpg
566 ms
nearys1.jpg
595 ms
nearys2.jpg
599 ms
nearys3.jpg
633 ms
stagshead1.jpg
644 ms
stagshead2.jpg
642 ms
stagshead3.jpg
668 ms
ferryman1.jpg
673 ms
ferryman2.jpg
677 ms
ferryman3.jpg
714 ms
hairylemon1.jpg
720 ms
hairylemon2.jpg
722 ms
hairylemon3.jpg
744 ms
mvcillairne1.jpg
746 ms
mvcillairne2.jpg
755 ms
mvcillairne3.jpg
806 ms
odonoghues1.jpg
808 ms
odonoghues2.jpg
809 ms
odonoghues3.jpg
820 ms
infowindow.js
66 ms
onion.js
19 ms
share_button.php
117 ms
ViewportInfoService.GetViewportInfo
135 ms
stats.js
30 ms
controls.js
26 ms
css
96 ms
transparent.png
48 ms
icon_pub.png
590 ms
google4.png
32 ms
mapcnt6.png
49 ms
sv5.png
86 ms
tmapctrl.png
58 ms
cb_scout5.png
78 ms
tmapctrl4.png
74 ms
imgs8.png
74 ms
qeKvIRsJabD.js
85 ms
LVx-xkvaJ0b.png
128 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
54 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
60 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
110 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
125 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
126 ms
vt
92 ms
vt
81 ms
vt
83 ms
vt
81 ms
vt
83 ms
vt
83 ms
vt
107 ms
vt
109 ms
vt
107 ms
vt
107 ms
vt
106 ms
vt
96 ms
vt
110 ms
vt
131 ms
vt
112 ms
vt
114 ms
vt
118 ms
vt
112 ms
vt
123 ms
vt
128 ms
vt
129 ms
vt
132 ms
vt
167 ms
vt
139 ms
vt
148 ms
vt
143 ms
vt
168 ms
vt
148 ms
vt
166 ms
vt
166 ms
jot
99 ms
AuthenticationService.Authenticate
53 ms
dublin.pub SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dublin.pub 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 Dublin.pub 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.
dublin.pub
Open Graph description is not detected on the main page of Dublin. 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: