Tools & Wizards About Us
behindthetower.org screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

behindthetower.org

Behind the Tower: New Histories of the UT Tower Shooting – Behind the Tower

Page Load Speed

971 ms in total

First Response

60 ms

Resources Loaded

268 ms

Page Rendered

643 ms

behindthetower.org screenshot

About Website

Welcome to behindthetower.org homepage info - get ready to check Behind The Tower best content for United States right away, or after learning these important things about behindthetower.org

Behind the Tower: New Histories of the UT Tower Shooting is a public history of the mass shooting that Charles Whitman carried out at UT Austin on August 1, 1966, the collective work of eleven graduat...

Visit behindthetower.org

Key Findings

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

Performance Metrics

behindthetower.org performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

behindthetower.org

60 ms

jquery-2.2.4.min.js

13 ms

bootstrap.min.css

22 ms

bigfoot-default.css

31 ms

lightbox.min.css

31 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 79% of them (19 requests) were addressed to the original Behindthetower.org, 8% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to I.creativecommons.org. The less responsive or slowest element that took the longest time to load (81 ms) relates to the external source I.creativecommons.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.0 kB (9%)

Content Size

527.2 kB

After Optimization

482.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Behindthetower.org main page is 527.2 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. 40% of websites need less resources to load. Images take 485.1 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 13.3 kB

  • Original 21.2 kB
  • After minification 20.6 kB
  • After compression 7.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. 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 13.3 kB or 63% of the original size.

Image Optimization

-7%

Potential reduce by 31.7 kB

  • Original 485.1 kB
  • After minification 453.4 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. Behind The Tower images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 7 (32%)

Requests Now

22

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

behindthetower.org

behindthetower.org

60 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

13 ms

bootstrap.min.css

bootstrap.min.css

22 ms

bigfoot-default.css

bigfoot-default.css

31 ms

lightbox.min.css

lightbox.min.css

31 ms

main.css

main.css

29 ms

bigfoot.min.js

bigfoot.min.js

36 ms

lightbox.min.js

lightbox.min.js

37 ms

hamburger.png

hamburger.png

62 ms

banner.png

banner.png

61 ms

88x31.png

88x31.png

81 ms

close.png

close.png

50 ms

loading.gif

loading.gif

50 ms

prev.png

prev.png

51 ms

next.png

next.png

51 ms

homepage-background.jpg

homepage-background.jpg

50 ms

homepage-banner.png

homepage-banner.png

52 ms

group-photo-1.jpg

group-photo-1.jpg

53 ms

group-photo-2.jpg

group-photo-2.jpg

51 ms

group-photo-3.jpg

group-photo-3.jpg

52 ms

analytics.js

analytics.js

23 ms

collect

collect

13 ms

88x31.png

88x31.png

50 ms

js

js

66 ms

Accessibility Review

behindthetower.org accessibility score

62

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

Best Practices

behindthetower.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

behindthetower.org SEO score

86

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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

behindthetower.org

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