Tools & Wizards About Us
tnng.annualleave.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

tnng.annualleave.com

Page Load Speed

8.6 sec in total

First Response

3.2 sec

Resources Loaded

5.2 sec

Page Rendered

98 ms

tnng.annualleave.com screenshot

About Website

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.com

Key Findings

We analyzed Tnng.annualleave.com page load time and found that the first response time was 3.2 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

tnng.annualleave.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value17.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value18.2 s

0/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.092

91/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

tnng.annualleave.com

3214 ms

tnng.annualleave.com

313 ms

jquery.js

145 ms

bootstrap.js

221 ms

jquery.dataTables.js

478 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 93% of them (69 requests) were addressed to the original Tnng.annualleave.com, 5% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Tnng.annualleave.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 460.7 kB (35%)

Content Size

1.3 MB

After Optimization

865.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tnng.annualleave.com 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. 45% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 11.5 kB

  • Original 14.4 kB
  • After minification 11.6 kB
  • After compression 2.9 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 2.8 kB, which is 19% 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 11.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 58.2 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.

JavaScript Optimization

-37%

Potential reduce by 441.1 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 749.9 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 441.1 kB or 37% of the original size.

CSS Optimization

-13%

Potential reduce by 8.2 kB

  • Original 62.7 kB
  • After minification 62.6 kB
  • After compression 54.5 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. Tnng.annualleave.com needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (89%)

Requests Now

66

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 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 44 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tnng.annualleave.com

tnng.annualleave.com

3214 ms

tnng.annualleave.com

tnng.annualleave.com

313 ms

jquery.js

jquery.js

145 ms

bootstrap.js

bootstrap.js

221 ms

jquery.dataTables.js

jquery.dataTables.js

478 ms

dataTables.bootstrap.js

dataTables.bootstrap.js

282 ms

dataTables.bootstrap.min.js

dataTables.bootstrap.min.js

282 ms

dataTables.foundation.js

dataTables.foundation.js

359 ms

dataTables.foundation.min.js

dataTables.foundation.min.js

378 ms

dataTables.jqueryui.js

dataTables.jqueryui.js

397 ms

dataTables.jqueryui.min.js

dataTables.jqueryui.min.js

397 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

578 ms

moment.js

moment.js

597 ms

sort-date.js

sort-date.js

543 ms

spectrum.js

spectrum.js

555 ms

angular.js

angular.js

747 ms

angular-datatables.js

angular-datatables.js

613 ms

angular-translate.js

angular-translate.js

637 ms

angular-cookies.js

angular-cookies.js

658 ms

angular-datatables.bootstrap.js

angular-datatables.bootstrap.js

667 ms

angular-flot.js

angular-flot.js

685 ms

angular-messages.js

angular-messages.js

713 ms

angular-no-captcha.js

angular-no-captcha.js

727 ms

angular-notify.js

angular-notify.js

738 ms

css

css

33 ms

angular-notify.css

angular-notify.css

743 ms

angular.rangeSlider.css

angular.rangeSlider.css

629 ms

bootstrap.css

bootstrap.css

566 ms

contents.css

contents.css

522 ms

custom.css

custom.css

550 ms

datatables.bootstrap.css

datatables.bootstrap.css

558 ms

editor.css

editor.css

534 ms

font-awesome.css

font-awesome.css

553 ms

font-oswald.css

font-oswald.css

506 ms

mvpready-admin.css

mvpready-admin.css

539 ms

ngDialog-theme-default.min.css

ngDialog-theme-default.min.css

538 ms

ngDialog.min.css

ngDialog.min.css

526 ms

select.css

select.css

527 ms

Site.css

Site.css

488 ms

spectrum.css

spectrum.css

496 ms

wizard.css

wizard.css

519 ms

angular-resource.js

angular-resource.js

511 ms

angular-sanitize.js

angular-sanitize.js

507 ms

angular-spectrum-colorpicker.js

angular-spectrum-colorpicker.js

513 ms

angular-stripe-checkout.js

angular-stripe-checkout.js

487 ms

angular-translate-loader-static-files.js

angular-translate-loader-static-files.js

467 ms

angular-ui-router.js

angular-ui-router.js

505 ms

angular.rangeSlider.js

angular.rangeSlider.js

501 ms

ckeditor.js

ckeditor.js

685 ms

config.js

config.js

484 ms

datetime-picker.js

datetime-picker.js

473 ms

isoCurrency.js

isoCurrency.js

471 ms

jquery.flot.js

jquery.flot.js

480 ms

jquery.flot.pie.js

jquery.flot.pie.js

466 ms

jquery.flot.time.js

jquery.flot.time.js

469 ms

ng-ckeditor.js

ng-ckeditor.js

470 ms

ng-lodash.js

ng-lodash.js

537 ms

ngDialog.js

ngDialog.js

473 ms

nsPopover.js

nsPopover.js

468 ms

select.js

select.js

466 ms

styles.js

styles.js

442 ms

ui-bootstrap-tpls.js

ui-bootstrap-tpls.js

484 ms

all.js

all.js

541 ms

locale-en.json

locale-en.json

78 ms

VerifySubdomain

VerifySubdomain

127 ms

login.tpl.html

login.tpl.html

81 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

20 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

116 ms

commonsettings

commonsettings

88 ms

Annual-Leave-Logo.png

Annual-Leave-Logo.png

88 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

6 ms

Oswald-Regular.ttf

Oswald-Regular.ttf

80 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

12 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

13 ms

Accessibility Review

tnng.annualleave.com accessibility score

74

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Document doesn't have a <title> element

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

<html> element does not have a [lang] attribute

Best Practices

tnng.annualleave.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tnng.annualleave.com SEO score

70

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: