2.9 sec in total
430 ms
2.3 sec
113 ms
Click here to check amazing Tnng Annualleave content for Ireland. Otherwise, check out these important facts you probably never knew about tnng.annualleave.com
Visit tnng.annualleave.comWe analyzed Tnng.annualleave.com page load time and found that the first response time was 430 ms and then it took 2.5 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.
tnng.annualleave.com performance score
name
value
score
weighting
Value18.0 s
0/100
10%
Value19.4 s
0/100
25%
Value19.2 s
0/100
10%
Value470 ms
60/100
30%
Value0.093
91/100
15%
Value19.1 s
3/100
10%
430 ms
385 ms
661 ms
172 ms
81 ms
Our browser made a total of 13 requests to load all elements on the main page. We found that 15% of them (2 requests) were addressed to the original Tnng.annualleave.com, 69% (9 requests) were made to Tnng.myannualleave.com and 8% (1 request) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (661 ms) relates to the external source Tnng.myannualleave.com.
Page size can be reduced by 404.3 kB (85%)
475.1 kB
70.7 kB
In fact, the total size of Tnng.annualleave.com main page is 475.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 447.1 kB which makes up the majority of the site volume.
Potential reduce by 12.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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 21% 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 12.2 kB or 74% of the original size.
Potential reduce by 903 B
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. Tnng Annualleave images are well optimized though.
Potential reduce by 390.8 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 390.8 kB or 87% of the original size.
Potential reduce by 463 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. Tnng.annualleave.com needs all CSS files to be minified and compressed as it can save up to 463 B or 59% of the original size.
Number of requests can be reduced by 5 (56%)
9
4
The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tnng Annualleave. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
tnng.annualleave.com
430 ms
tnng.annualleave.com
385 ms
tnng.myannualleave.com
661 ms
login.aspx
172 ms
Login.css
81 ms
WebResource.axd
162 ms
ScriptResource.axd
275 ms
ScriptResource.axd
324 ms
ScriptResource.axd
404 ms
WebResource.axd
341 ms
Logo60x200.png
336 ms
feedback-v2.js
230 ms
feedback_trans_tab-fa5bd26fde4425fd8102f4380980fc11.png
39 ms
tnng.annualleave.com 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
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
Document doesn't have a <title> element
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
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
tnng.annualleave.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
tnng.annualleave.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Tnng.annualleave.com 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 Tnng.annualleave.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.
tnng.annualleave.com
Open Graph description is not detected on the main page of Tnng Annualleave. 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: