8.7 sec in total
435 ms
7.4 sec
828 ms
Welcome to wearedublin.com homepage info - get ready to check Weare Dublin best content for Ireland right away, or after learning these important things about wearedublin.com
Dublin GAA news, events, fan opinions, behind the scenes interviews and competitions across All Four Codes
Visit wearedublin.comWe analyzed Wearedublin.com page load time and found that the first response time was 435 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wearedublin.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value7.2 s
5/100
25%
Value5.5 s
54/100
10%
Value890 ms
32/100
30%
Value0
100/100
15%
Value6.7 s
56/100
10%
435 ms
2311 ms
276 ms
294 ms
10 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 58% of them (69 requests) were addressed to the original Wearedublin.com, 18% (21 requests) were made to Scontent.cdninstagram.com and 8% (9 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Wearedublin.com.
Page size can be reduced by 541.7 kB (12%)
4.4 MB
3.8 MB
In fact, the total size of Wearedublin.com main page is 4.4 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. 65% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 66.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 66.2 kB or 82% of the original size.
Potential reduce by 44.1 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. Weare Dublin images are well optimized though.
Potential reduce by 253.2 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 253.2 kB or 69% of the original size.
Potential reduce by 178.2 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. Wearedublin.com needs all CSS files to be minified and compressed as it can save up to 178.2 kB or 83% of the original size.
Number of requests can be reduced by 59 (52%)
114
55
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weare 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 19 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
wearedublin.com
435 ms
www.wearedublin.com
2311 ms
wp-emoji-release.min.js
276 ms
sb-instagram.css
294 ms
font-awesome.min.css
10 ms
symple_shortcodes_styles.css
374 ms
default.min.css
277 ms
pagenavi-css.css
283 ms
easy-twitter-feed-widget.css
356 ms
jquery.js
827 ms
jquery-migrate.min.js
560 ms
widgetkit-e1b70dd8.css
751 ms
widgetkit-fac88b56.js
668 ms
wpdg.js
643 ms
base.css
646 ms
layout.css
864 ms
menus.css
923 ms
modules.css
922 ms
tools.css
955 ms
system.css
1032 ms
extensions.css
1111 ms
custom.css
1113 ms
animations.css
1199 ms
street.css
1202 ms
yanonekaffeesatz.css
1226 ms
bebas.css
1319 ms
style.css
1399 ms
print.css
1397 ms
css
26 ms
bebas.css
1472 ms
warp.js
1473 ms
accordionmenu.js
1497 ms
dropdownmenu.js
1601 ms
template.js
1682 ms
wp-power-stats.js
1616 ms
sb-instagram.js
1776 ms
widget-easy-twitter-feed-widget.js
1695 ms
lightbox.js
1008 ms
mediaelement-and-player.js
1298 ms
spotlight.js
1114 ms
wadheaderlonglogo2.3.png
1595 ms
img_2541-1-150x150.jpg
1289 ms
img_2387-1-150x150.jpg
1261 ms
img_2344-1-150x150.jpg
1287 ms
img_2291-1-150x150.jpg
1383 ms
img_2257-1-150x150.jpg
1574 ms
PPMar19th-150x150.jpg
1570 ms
img_2247-150x150.jpg
1573 ms
img_2245-1-150x150.jpg
1579 ms
AHLKilkenny-150x150.jpg
1664 ms
img_2243-3-150x150.jpg
1844 ms
base.css
1854 ms
layout.css
1858 ms
modules.css
1801 ms
menus.css
1810 ms
tools.css
1845 ms
system.css
1955 ms
system.css
1882 ms
system-all.css
1887 ms
print.css
1614 ms
system_continue_reading.png
151 ms
pagination.png
305 ms
loader.png
304 ms
module_icons.png
305 ms
street_img.jpg
1601 ms
module_box_transparency75.png
305 ms
BebasNeue-webfont.woff
478 ms
YDAoLskQQ5MOAgvHUQCcLbvy90DtE_Pg_qiF9bHvTzw.ttf
76 ms
We_iSDqttE3etzfdfhuPRX4NhRhUVU1NOvrEWRXSCoI.ttf
78 ms
fontawesome-webfont.woff
77 ms
analytics.js
76 ms
admin-ajax.php
1016 ms
widgets.js
108 ms
widgets.js
50 ms
all.js
49 ms
1414902489
81 ms
recent
195 ms
close.png
519 ms
blank.gif
519 ms
menu_dropdown_dropdown.png
529 ms
collect
41 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
22 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
21 ms
227 ms
syndication
171 ms
344713329262084096
191 ms
11116847_962429147115022_1971551841_a.jpg
129 ms
xd_arbiter.php
78 ms
xd_arbiter.php
125 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
58 ms
1208364_557828407722164_1624922185_n.jpg
33 ms
12826080_1793021917585645_1800259952_n.jpg
74 ms
12816974_1102100696508015_310876173_n.jpg
67 ms
12798011_1831176123776014_1237859544_n.jpg
71 ms
10817760_997599633647480_241728315_n.jpg
53 ms
12797913_1693504724265507_516390759_n.jpg
104 ms
10593499_1559058911070858_364218246_n.jpg
109 ms
929134_844244829037713_414995894_n.jpg
58 ms
1391175_1122436934441871_1653155218_n.jpg
125 ms
10848184_234228513591697_342542636_n.jpg
74 ms
926415_1521723938133728_1435355738_n.jpg
141 ms
1172493_591670084341037_135990004_n.jpg
88 ms
12677367_1076113819118729_250757748_n.jpg
87 ms
10956805_940598772702441_545803138_n.jpg
94 ms
12523618_1695580814031302_2143709286_n.jpg
148 ms
10561194_1525447887751469_1507930849_n.jpg
109 ms
12822548_691884310951503_1699740548_n.jpg
138 ms
12826306_223776484641375_1550775809_n.jpg
181 ms
12816986_1729665937277141_324973315_n.jpg
148 ms
12818964_198888377150084_2114632871_n.jpg
181 ms
proxy.jpg
510 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
8 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
7 ms
jot.html
6 ms
cSUr-mEU_normal.jpg
77 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
82 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
81 ms
proxy.jpg
438 ms
jot.html
2 ms
wearedublin.com 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.
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
Links do not have a discernible name
wearedublin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
wearedublin.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 Wearedublin.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 Wearedublin.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.
wearedublin.com
Open Graph data is detected on the main page of Weare Dublin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: