Tools & Wizards About Us
nibtt.net screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

nibtt.net

The National Insurance Board of Trinidad and Tobago (NIBTT)

Page Load Speed

1.8 sec in total

First Response

49 ms

Resources Loaded

1.2 sec

Page Rendered

563 ms

nibtt.net screenshot

About Website

Visit nibtt.net now to see the best up-to-date NIBTT content for Trinidad and Tobago and also check out these interesting facts you probably never knew about nibtt.net

National Insurance information on the Registration and Benefits process and requirements for residents of Trinidad and Tobago

Visit nibtt.net

Key Findings

We analyzed Nibtt.net page load time and found that the first response time was 49 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

nibtt.net performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

nibtt.net

49 ms

nibtt.net

77 ms

bootstrap.min.css

29 ms

bootstrap.bundle.min.js

44 ms

style_index_2022_RS.css

22 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 39% of them (24 requests) were addressed to the original Nibtt.net, 48% (29 requests) were made to Static.cdninstagram.com and 7% (4 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (631 ms) relates to the external source Instagram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 704.2 kB (12%)

Content Size

5.9 MB

After Optimization

5.2 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Nibtt.net main page is 5.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. 70% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 30.3 kB

  • Original 37.0 kB
  • After minification 24.7 kB
  • After compression 6.7 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 12.4 kB, which is 33% 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 30.3 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 669.2 kB

  • Original 5.8 MB
  • After minification 5.2 MB

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, NIBTT needs image optimization as it can save up to 669.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-83%

Potential reduce by 4.7 kB

  • Original 5.7 kB
  • After minification 3.0 kB
  • After compression 961 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. Nibtt.net needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

59

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NIBTT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

nibtt.net

nibtt.net

49 ms

nibtt.net

nibtt.net

77 ms

bootstrap.min.css

bootstrap.min.css

29 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

44 ms

style_index_2022_RS.css

style_index_2022_RS.css

22 ms

embed.js

embed.js

141 ms

nibLogo70px.png

nibLogo70px.png

37 ms

facebook.svg

facebook.svg

14 ms

instagram.svg

instagram.svg

15 ms

youtube.svg

youtube.svg

26 ms

phone-vibrate-fill.svg

phone-vibrate-fill.svg

27 ms

envelope-fill.svg

envelope-fill.svg

39 ms

telephone-fill.svg

telephone-fill.svg

39 ms

dyk20240308.jpeg

dyk20240308.jpeg

106 ms

banner_ar2022_23.png

banner_ar2022_23.png

187 ms

OP20230822.png

OP20230822.png

113 ms

abc3.png

abc3.png

152 ms

appointmentportalad2.JPG

appointmentportalad2.JPG

106 ms

Claims_Guidelines_Checklist_2022.jpg

Claims_Guidelines_Checklist_2022.jpg

128 ms

WifiPage-CoC_2022.jpg

WifiPage-CoC_2022.jpg

137 ms

WifiPage-Pay-Online_2022.jpg

WifiPage-Pay-Online_2022.jpg

143 ms

cont-statement-request-2.jpg

cont-statement-request-2.jpg

151 ms

NI184-Alert-2.jpg

NI184-Alert-2.jpg

154 ms

AR2022_23.jpg

AR2022_23.jpg

175 ms

iloTenthAV2.jpg

iloTenthAV2.jpg

173 ms

dyk1.png

dyk1.png

247 ms

clock-fill.svg

clock-fill.svg

187 ms

631 ms

GvOYVBCkVVx.css

GvOYVBCkVVx.css

48 ms

TUNtZllrzdj.css

TUNtZllrzdj.css

58 ms

CU3upjzumaA.css

CU3upjzumaA.css

59 ms

0UKWGpiF5VA.css

0UKWGpiF5VA.css

61 ms

nSAeVcTyw4J.css

nSAeVcTyw4J.css

62 ms

VWDhCULazb5.js

VWDhCULazb5.js

65 ms

51661769_2309425365969275_647595044336828416_n.jpg

51661769_2309425365969275_647595044336828416_n.jpg

45 ms

bfm4wPeSpxk.js

bfm4wPeSpxk.js

30 ms

mras9avKshL.js

mras9avKshL.js

29 ms

oS9Nfw0_iQb.js

oS9Nfw0_iQb.js

28 ms

411NZMSLECE.js

411NZMSLECE.js

29 ms

9lDiey1l9HS.js

9lDiey1l9HS.js

27 ms

5KQMD4fCUhW.js

5KQMD4fCUhW.js

49 ms

0yactC7tM6g.js

0yactC7tM6g.js

48 ms

snf_jZmdlHM.js

snf_jZmdlHM.js

53 ms

jVvSDzaDazm.js

jVvSDzaDazm.js

52 ms

Zt0P0Kz5jRk.js

Zt0P0Kz5jRk.js

52 ms

J1VbMx8qJ8X.js

J1VbMx8qJ8X.js

53 ms

7571VQXCJLv.js

7571VQXCJLv.js

65 ms

DWX0oO3Sj_H.js

DWX0oO3Sj_H.js

61 ms

hQsYm2vl4V8.js

hQsYm2vl4V8.js

64 ms

CGFN-zBXPPc.js

CGFN-zBXPPc.js

64 ms

9mS1iFuh_oZ.js

9mS1iFuh_oZ.js

64 ms

5-CNhD1hzUM.js

5-CNhD1hzUM.js

64 ms

HDiX03ZTkcn.js

HDiX03ZTkcn.js

66 ms

zFPG9TYvU6b.js

zFPG9TYvU6b.js

69 ms

7Zc7zfJz1TP.js

7Zc7zfJz1TP.js

68 ms

j0ThrVohGRE.js

j0ThrVohGRE.js

67 ms

IbEU6o3x0eh.js

IbEU6o3x0eh.js

66 ms

440943464_843732554464470_6478418469804197632_n.jpg

440943464_843732554464470_6478418469804197632_n.jpg

50 ms

441604335_843724051131987_4015742026324095661_n.jpg

441604335_843724051131987_4015742026324095661_n.jpg

63 ms

442414230_843726167798442_6278930232414899957_n.jpg

442414230_843726167798442_6278930232414899957_n.jpg

62 ms

hwgTSgiJXcc.png

hwgTSgiJXcc.png

65 ms

Accessibility Review

nibtt.net accessibility score

90

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

nibtt.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

nibtt.net SEO score

98

Search Engine Optimization Advices

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

    EN

  • Encoding

    ISO-8859-1.0

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nibtt.net 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 Nibtt.net main page’s claimed encoding is iso-8859-1.0. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

nibtt.net

Open Graph description is not detected on the main page of NIBTT. 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: