Tools & Wizards About Us
fablab.uta.edu screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

fablab.uta.edu

FabLab | UTA Libraries

Page Load Speed

44.8 sec in total

First Response

10.8 sec

Resources Loaded

32.6 sec

Page Rendered

1.3 sec

fablab.uta.edu screenshot

About Website

Welcome to fablab.uta.edu homepage info - get ready to check Fab Lab UTA best content for United States right away, or after learning these important things about fablab.uta.edu

Visit fablab.uta.edu

Key Findings

We analyzed Fablab.uta.edu page load time and found that the first response time was 10.8 sec and then it took 33.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

fablab.uta.edu performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.286

42/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

fablab.uta.edu

10849 ms

system.base.css

327 ms

calendar_multiday.css

351 ms

date.css

272 ms

datepicker.1.7.css

274 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 62% of them (49 requests) were addressed to the original Fablab.uta.edu, 19% (15 requests) were made to Youtube-nocookie.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Fablab-test.uta.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.1 MB (51%)

Content Size

14.1 MB

After Optimization

7.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fablab.uta.edu main page is 14.1 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. 60% of websites need less resources to load. Images take 13.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 23.3 kB

  • Original 29.8 kB
  • After minification 27.7 kB
  • After compression 6.5 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 23.3 kB or 78% of the original size.

Image Optimization

-49%

Potential reduce by 6.4 MB

  • Original 13.2 MB
  • After minification 6.7 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, Fab Lab UTA needs image optimization as it can save up to 6.4 MB or 49% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 282.9 kB

  • Original 442.9 kB
  • After minification 398.2 kB
  • After compression 160.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 282.9 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 385.1 kB

  • Original 458.9 kB
  • After minification 416.6 kB
  • After compression 73.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. Fablab.uta.edu needs all CSS files to be minified and compressed as it can save up to 385.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (68%)

Requests Now

65

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fab Lab UTA. 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 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fablab.uta.edu

fablab.uta.edu

10849 ms

system.base.css

system.base.css

327 ms

calendar_multiday.css

calendar_multiday.css

351 ms

date.css

date.css

272 ms

datepicker.1.7.css

datepicker.1.7.css

274 ms

field.css

field.css

307 ms

node.css

node.css

337 ms

office_hours.css

office_hours.css

331 ms

youtube.css

youtube.css

314 ms

views.css

views.css

359 ms

ctools.css

ctools.css

358 ms

panels.css

panels.css

366 ms

flexslider_img.css

flexslider_img.css

367 ms

flexslider.css

flexslider.css

372 ms

custom_search.css

custom_search.css

392 ms

improved_multi_select.css

improved_multi_select.css

394 ms

style.css

style.css

696 ms

modernizr.custom.07603.js

modernizr.custom.07603.js

490 ms

jquery.min.js

jquery.min.js

281 ms

jquery.once.js

jquery.once.js

414 ms

drupal.js

drupal.js

475 ms

fablab.uta.edu

fablab.uta.edu

1801 ms

custom_search.js

custom_search.js

462 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

536 ms

googleanalytics.js

googleanalytics.js

501 ms

improved_multi_select.js

improved_multi_select.js

485 ms

affix.js

affix.js

477 ms

alert.js

alert.js

538 ms

button.js

button.js

565 ms

carousel.js

carousel.js

565 ms

collapse.js

collapse.js

574 ms

dropdown.js

dropdown.js

907 ms

modal.js

modal.js

905 ms

tooltip.js

tooltip.js

895 ms

popover.js

popover.js

895 ms

scrollspy.js

scrollspy.js

894 ms

tab.js

tab.js

892 ms

transition.js

transition.js

763 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

761 ms

back2top.js

back2top.js

762 ms

flexslider.load.js

flexslider.load.js

751 ms

bootstrap.js

bootstrap.js

766 ms

analytics.js

analytics.js

157 ms

thinktable_revised_1800x600.png

thinktable_revised_1800x600.png

15373 ms

solderingblue_revised_1800x600.png

solderingblue_revised_1800x600.png

13864 ms

bicycle_1800x600.png

bicycle_1800x600.png

11391 ms

brain2_1800x600.png

brain2_1800x600.png

5300 ms

UTAlogo.png

UTAlogo.png

185 ms

FLlogo_260.png

FLlogo_260.png

185 ms

search-button.png

search-button.png

1107 ms

Library-Logo-vertical.jpg

Library-Logo-vertical.jpg

1095 ms

sdk.js

sdk.js

1341 ms

Lightbulb.png

Lightbulb.png

20034 ms

Qsz_EM0xIqo

Qsz_EM0xIqo

348 ms

ullJRSWGllI

ullJRSWGllI

345 ms

wAurN-N2QMc

wAurN-N2QMc

345 ms

P-oE5e6y9Gs

P-oE5e6y9Gs

344 ms

i0RN5rvf8rs

i0RN5rvf8rs

343 ms

collect

collect

847 ms

wAurN-N2QMc

wAurN-N2QMc

43 ms

i0RN5rvf8rs

i0RN5rvf8rs

32 ms

ullJRSWGllI

ullJRSWGllI

31 ms

P-oE5e6y9Gs

P-oE5e6y9Gs

30 ms

Qsz_EM0xIqo

Qsz_EM0xIqo

23 ms

wAurN-N2QMc

wAurN-N2QMc

792 ms

i0RN5rvf8rs

i0RN5rvf8rs

828 ms

ullJRSWGllI

ullJRSWGllI

732 ms

P-oE5e6y9Gs

P-oE5e6y9Gs

747 ms

Qsz_EM0xIqo

Qsz_EM0xIqo

743 ms

88x31.png

88x31.png

396 ms

www-embed-player-vfl5foy2V.css

www-embed-player-vfl5foy2V.css

392 ms

www-embed-player.js

www-embed-player.js

661 ms

954 ms

xd_arbiter.php

xd_arbiter.php

1052 ms

xd_arbiter.php

xd_arbiter.php

1354 ms

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

490 ms

ad_status.js

ad_status.js

818 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

576 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

667 ms

Accessibility Review

fablab.uta.edu accessibility score

100

Accessibility Issues

Best Practices

fablab.uta.edu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fablab.uta.edu SEO score

81

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 Fablab.uta.edu 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 Fablab.uta.edu 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

fablab.uta.edu

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