2.2 sec in total
188 ms
1.2 sec
775 ms
Click here to check amazing Too Far content. Otherwise, check out these important facts you probably never knew about toofar.com
Rich Shapero’s Too Far combines his novel with original music and stunning visual art to create an immersive storytelling experience.
Visit toofar.comWe analyzed Toofar.com page load time and found that the first response time was 188 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 35% of websites can load faster.
toofar.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value7.6 s
4/100
25%
Value25.9 s
0/100
10%
Value560 ms
52/100
30%
Value0.083
94/100
15%
Value77.1 s
0/100
10%
188 ms
218 ms
207 ms
44 ms
73 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 60% of them (26 requests) were addressed to the original Toofar.com, 7% (3 requests) were made to Ajax.googleapis.com and 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (462 ms) belongs to the original domain Toofar.com.
Page size can be reduced by 199.2 kB (14%)
1.4 MB
1.2 MB
In fact, the total size of Toofar.com main page is 1.4 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 19.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 3.9 kB, which is 15% 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 19.7 kB or 74% of the original size.
Potential reduce by 47.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. Too Far images are well optimized though.
Potential reduce by 90.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 90.9 kB or 58% of the original size.
Potential reduce by 41.3 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. Toofar.com needs all CSS files to be minified and compressed as it can save up to 41.3 kB or 83% of the original size.
Number of requests can be reduced by 11 (27%)
41
30
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Too Far. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
toofar.com
188 ms
www.toofar.com
218 ms
css.css
207 ms
jquery.min.js
44 ms
jquery-ui.min.js
73 ms
swfobject.js
61 ms
sitewide.js
252 ms
shadowbox.css
147 ms
shadowbox.js
284 ms
counter.js
7 ms
toofar_bg_2.jpg
344 ms
1.jpg
280 ms
2.jpg
252 ms
facebook.png
77 ms
twitter.png
150 ms
too_far_novel.png
343 ms
landing_p01b.jpg
292 ms
visual_art_evb.jpg
340 ms
ga.js
19 ms
toofar_bg_wrapper.jpg
396 ms
too_far_header.jpg
413 ms
too_far_logo.png
361 ms
logo_sm.png
406 ms
app-base.png
406 ms
quote.png
407 ms
all.js
61 ms
widgets.js
134 ms
read_button.png
411 ms
cd_dawn_remembers.png
437 ms
gallery_buttons_music.png
458 ms
store_icons_6.png
456 ms
fade_d6d6d6.png
457 ms
gallery_buttons_sidebar.png
462 ms
t.php
104 ms
player_api
27 ms
__utm.gif
41 ms
www-widgetapi.js
65 ms
__utm.gif
62 ms
66 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
137 ms
xd_arbiter.php
28 ms
xd_arbiter.php
45 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
44 ms
toofar.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
toofar.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
toofar.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toofar.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 Toofar.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.
toofar.com
Open Graph description is not detected on the main page of Too Far. 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: