4.5 sec in total
276 ms
3.2 sec
1 sec
Click here to check amazing Headline content. Otherwise, check out these important facts you probably never knew about headline.ie
Headline is Ireland’s national media programme for responsible reporting, and representation of mental ill health and suicide.
Visit headline.ieWe analyzed Headline.ie page load time and found that the first response time was 276 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
headline.ie performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value9.1 s
1/100
25%
Value10.6 s
7/100
10%
Value1,060 ms
25/100
30%
Value0.057
98/100
15%
Value13.5 s
11/100
10%
276 ms
1175 ms
38 ms
92 ms
184 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 75% of them (64 requests) were addressed to the original Headline.ie, 19% (16 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Headline.ie.
Page size can be reduced by 297.0 kB (23%)
1.3 MB
1.0 MB
In fact, the total size of Headline.ie main page is 1.3 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. Javascripts take 459.9 kB which makes up the majority of the site volume.
Potential reduce by 155.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 155.1 kB or 82% of the original size.
Potential reduce by 55.0 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. Obviously, Headline needs image optimization as it can save up to 55.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 39.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.
Potential reduce by 47.9 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. Headline.ie needs all CSS files to be minified and compressed as it can save up to 47.9 kB or 22% of the original size.
Number of requests can be reduced by 51 (80%)
64
13
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Headline. 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 from 24 to 1 for CSS and as a result speed up the page load time.
headline.ie
276 ms
headline.ie
1175 ms
font-awesome.min.css
38 ms
sogo-accessibility-public.css
92 ms
cookieblocker.min.css
184 ms
elementor-icons.min.css
269 ms
custom-frontend-lite.min.css
276 ms
swiper.min.css
285 ms
post-6253.css
285 ms
custom-pro-frontend-lite.min.css
286 ms
post-7666.css
293 ms
post-6257.css
358 ms
post-6264.css
364 ms
ecs-style.css
380 ms
style-static.min.css
664 ms
fontawesome.min.css
477 ms
solid.min.css
389 ms
brands.min.css
445 ms
jquery.min.js
458 ms
jquery-migrate.min.js
474 ms
page-transitions.min.js
488 ms
ecs_ajax_pagination.js
534 ms
ecs.js
548 ms
js
64 ms
api.js
42 ms
api.js
62 ms
custom-widget-icon-list.min.css
569 ms
custom-pro-widget-nav-menu.min.css
570 ms
widget-theme-elements.min.css
585 ms
widget-nested-carousel.min.css
621 ms
custom-pro-widget-call-to-action.min.css
635 ms
custom-widget-icon-box.min.css
829 ms
widget-loop-builder.min.css
829 ms
animations.min.css
839 ms
lazysizes.min.js
840 ms
navigation.js
890 ms
sogo-accessibility-public.js
890 ms
scripts.min.js
998 ms
instant-page.min.js
890 ms
common.js
889 ms
complianz.min.js
889 ms
jquery.sticky.min.js
977 ms
jquery.smartmenus.min.js
899 ms
imagesloaded.min.js
808 ms
webpack-pro.runtime.min.js
721 ms
webpack.runtime.min.js
709 ms
frontend-modules.min.js
808 ms
hooks.min.js
848 ms
i18n.min.js
806 ms
frontend.min.js
841 ms
waypoints.min.js
777 ms
core.min.js
770 ms
frontend.min.js
793 ms
elements-handlers.min.js
782 ms
recaptcha__en.js
186 ms
Shine-Logo-White-PNG-1.png
559 ms
headline_logo_soluswhite.png
532 ms
Headline-BG-resized-FullBrand.png
631 ms
Headline-BG-Grey.png
792 ms
Headline-BG-Generic2-300x86-1.png
531 ms
Headline-BG-Generic2.png
687 ms
cfl-logo-white.png
629 ms
headline_logowide_white.png
630 ms
shine-logo-2020-wht.png
677 ms
sogo-logo.png
833 ms
Headline-BG-Consult.png
742 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilXvVUg.ttf
118 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClXvVUg.ttf
139 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVilXvVUg.ttf
153 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5XvVUg.ttf
157 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5XvVUg.ttf
156 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVi5XvVUg.ttf
156 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4Gfy5XvVUg.ttf
154 ms
fa-solid-900.woff
836 ms
fa-brands-400.woff
740 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
153 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
156 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
236 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
237 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
237 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
237 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
239 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
239 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
240 ms
eicons.woff
917 ms
headline.ie 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
[aria-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
headline.ie 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
headline.ie 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Headline.ie 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 Headline.ie 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.
headline.ie
Open Graph data is detected on the main page of Headline. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: