Tools & Wizards About Us
t11.org screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

t11.org

Fibre Channel - INCITS

Page Load Speed

2.6 sec in total

First Response

578 ms

Resources Loaded

1.8 sec

Page Rendered

197 ms

t11.org screenshot

About Website

Welcome to t11.org homepage info - get ready to check T 11 best content right away, or after learning these important things about t11.org

The INCITS/Fibre Channel Technical Committee is responsible for the development of the Fibre Channel (FC) standards. These standards specify the following:Physical variants and interfaces; Framing, si...

Visit t11.org

Key Findings

We analyzed T11.org page load time and found that the first response time was 578 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

t11.org performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

t11

578 ms

css

39 ms

css

55 ms

common.css

39 ms

js-image-slider.css

75 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original T11.org, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (578 ms) relates to the external source Incits.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.6 kB (5%)

Content Size

2.3 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of T11.org main page is 2.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. 30% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 40.0 kB

  • Original 46.7 kB
  • After minification 26.9 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 19.8 kB, which is 42% 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 40.0 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 78.8 kB

  • Original 2.1 MB
  • After minification 2.1 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. T 11 images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 6.8 kB

  • Original 106.1 kB
  • After minification 106.1 kB
  • After compression 99.4 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.

Requests Breakdown

Number of requests can be reduced by 18 (33%)

Requests Now

55

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

t11

t11

578 ms

css

css

39 ms

css

css

55 ms

common.css

common.css

39 ms

js-image-slider.css

js-image-slider.css

75 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

142 ms

jquery.tools.min.js

jquery.tools.min.js

178 ms

jquery.dropkick-1.0.0.js

jquery.dropkick-1.0.0.js

109 ms

js-image-slider.js

js-image-slider.js

112 ms

js

js

68 ms

technical-committees.css

technical-committees.css

112 ms

dropkick.css

dropkick.css

113 ms

jquery.cycle.all.js

jquery.cycle.all.js

204 ms

plugins.js

plugins.js

150 ms

background-top.jpg

background-top.jpg

72 ms

background-left.jpg

background-left.jpg

54 ms

background-right.jpg

background-right.jpg

76 ms

logo.png

logo.png

55 ms

search.jpg

search.jpg

56 ms

linkedin.png

linkedin.png

53 ms

facebook.jpg

facebook.jpg

69 ms

twitter.jpg

twitter.jpg

71 ms

join_incits_icon.jpg

join_incits_icon.jpg

75 ms

menubar.jpg

menubar.jpg

77 ms

memberlogin-back.jpg

memberlogin-back.jpg

104 ms

member_login_icon.jpg

member_login_icon.jpg

105 ms

person.png

person.png

107 ms

red_square.png

red_square.png

111 ms

aeede2b9-8419-4132-a706-45139933b99b.jpg

aeede2b9-8419-4132-a706-45139933b99b.jpg

113 ms

406450d8-6cde-4cfb-bb7b-9f8f02289685.png

406450d8-6cde-4cfb-bb7b-9f8f02289685.png

148 ms

1216ba50-8c1d-47aa-a2e0-7742da4d3362.jpg

1216ba50-8c1d-47aa-a2e0-7742da4d3362.jpg

201 ms

4c03221e-edaa-43d0-b97d-65b5ed855181.jpg

4c03221e-edaa-43d0-b97d-65b5ed855181.jpg

139 ms

40ad1bd1-9078-4195-a00b-a741c18125df.jpg

40ad1bd1-9078-4195-a00b-a741c18125df.jpg

144 ms

4ce22cc3-ad0f-4e1f-a519-cca49fe5e5e3.jpg

4ce22cc3-ad0f-4e1f-a519-cca49fe5e5e3.jpg

319 ms

b317317b-7a14-4450-98a9-46b00401c3b3.jpg

b317317b-7a14-4450-98a9-46b00401c3b3.jpg

186 ms

a61d11cc-80d4-4e87-bb5a-76809f2574a6.jpg

a61d11cc-80d4-4e87-bb5a-76809f2574a6.jpg

174 ms

5b88b755-cedf-4d66-a6ab-f1c097399e6d.jpg

5b88b755-cedf-4d66-a6ab-f1c097399e6d.jpg

249 ms

b16e166b-51a0-4e69-8e43-e566f6dd5621.jpg

b16e166b-51a0-4e69-8e43-e566f6dd5621.jpg

185 ms

b28bad72-df1a-4eae-a6df-1f031b8f0853.jpg

b28bad72-df1a-4eae-a6df-1f031b8f0853.jpg

209 ms

a4071436-8986-4c4b-9f84-1f7a9e4b8b05.png

a4071436-8986-4c4b-9f84-1f7a9e4b8b05.png

223 ms

823e3031-d881-4a44-99a8-cc893e852d15.jpg

823e3031-d881-4a44-99a8-cc893e852d15.jpg

224 ms

39e0d2af-9100-4044-b685-277df12119b0.jpg

39e0d2af-9100-4044-b685-277df12119b0.jpg

234 ms

99ae1096-51f5-45e2-9b3c-2f49c5a15193.jpg

99ae1096-51f5-45e2-9b3c-2f49c5a15193.jpg

244 ms

f0601ca0-4a23-45d5-ad55-c334df054bdb.jpg

f0601ca0-4a23-45d5-ad55-c334df054bdb.jpg

260 ms

6eeb2a13-5c59-4ff9-bfd4-eb31616b4968.png

6eeb2a13-5c59-4ff9-bfd4-eb31616b4968.png

261 ms

b2c829fd-7ab5-442d-8fb2-7637cd6d75a4.jpg

b2c829fd-7ab5-442d-8fb2-7637cd6d75a4.jpg

267 ms

a836da25-1dfd-4749-9a0f-304eb8a048be.jpg

a836da25-1dfd-4749-9a0f-304eb8a048be.jpg

278 ms

a54383a2-8685-4ec7-8869-a53d01d035e5.png

a54383a2-8685-4ec7-8869-a53d01d035e5.png

286 ms

daf4b87e-15ba-4f46-a3b3-abf670723323.jpg

daf4b87e-15ba-4f46-a3b3-abf670723323.jpg

440 ms

font

font

21 ms

font

font

47 ms

6b10842b-b3c9-45b8-ae83-9f0f987c5de9.png

6b10842b-b3c9-45b8-ae83-9f0f987c5de9.png

298 ms

navi-line.jpg

navi-line.jpg

251 ms

menu-opened.png

menu-opened.png

261 ms

navi-arrow.png

navi-arrow.png

270 ms

dropdown.jpg

dropdown.jpg

283 ms

Accessibility Review

t11.org accessibility score

82

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

Best Practices

t11.org best practices score

75

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

SEO Factors

t11.org SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise T11.org 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 T11.org 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

t11.org

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