675 ms in total
85 ms
380 ms
210 ms
Visit seejohnrun.com now to see the best up-to-date See John Run content and also check out these interesting facts you probably never knew about seejohnrun.com
seejohnrun.com documented my 3,800+ mile solo and unsupported run across America in 2004-2005. Visit usacrossers.com for all the latest and historical transcontinental crossings.
Visit seejohnrun.comWe analyzed Seejohnrun.com page load time and found that the first response time was 85 ms and then it took 590 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
seejohnrun.com performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value5.0 s
27/100
25%
Value1.0 s
100/100
10%
Value20 ms
100/100
30%
Value0.158
74/100
15%
Value1.6 s
100/100
10%
85 ms
53 ms
56 ms
9 ms
48 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 94% of them (58 requests) were addressed to the original Seejohnrun.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Www2.clustrmaps.com. The less responsive or slowest element that took the longest time to load (191 ms) belongs to the original domain Seejohnrun.com.
Page size can be reduced by 85.1 kB (6%)
1.5 MB
1.4 MB
In fact, the total size of Seejohnrun.com main page is 1.5 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 1.4 MB which makes up the majority of the site volume.
Potential reduce by 11.2 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 11.2 kB or 75% of the original size.
Potential reduce by 44.8 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. See John Run images are well optimized though.
Potential reduce by 29.1 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 29.1 kB or 63% of the original size.
We found no issues to fix!
59
59
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of See John Run. According to our analytics all requests are already optimized.
seejohnrun.com
85 ms
usacrossers.gif
53 ms
index2.php
56 ms
ga.js
9 ms
logo.jpg
48 ms
sign1.jpg
53 ms
sign2.jpg
53 ms
sign3.jpg
57 ms
sign4.jpg
51 ms
sign5.jpg
50 ms
sign6.jpg
52 ms
sign7.jpg
61 ms
sign8.jpg
66 ms
prequel.jpg
76 ms
morningmoviestill.jpg
80 ms
policeescort.jpg
81 ms
finishmoviestill.jpg
86 ms
awardstill.jpg
93 ms
10.jpg
84 ms
20.jpg
126 ms
30.jpg
97 ms
40.jpg
115 ms
50.jpg
119 ms
60.jpg
113 ms
70.jpg
109 ms
80.jpg
130 ms
90.jpg
143 ms
100.jpg
147 ms
110.jpg
143 ms
120.jpg
136 ms
130.jpg
154 ms
140.jpg
147 ms
150.jpg
162 ms
160.jpg
178 ms
170.jpg
177 ms
180.jpg
167 ms
190.jpg
164 ms
200.jpg
181 ms
finishocean.jpg
191 ms
10.jpg
181 ms
__utm.gif
12 ms
20.jpg
143 ms
30.jpg
157 ms
40.jpg
146 ms
50.jpg
156 ms
60.jpg
154 ms
70.jpg
163 ms
index2.php
116 ms
80.jpg
159 ms
90.jpg
156 ms
100.jpg
166 ms
110.jpg
153 ms
120.jpg
167 ms
130.jpg
152 ms
140.jpg
173 ms
150.jpg
181 ms
160.jpg
166 ms
170.jpg
170 ms
180.jpg
155 ms
190.jpg
157 ms
200.jpg
158 ms
progress.jpg
176 ms
seejohnrun.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
seejohnrun.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
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
seejohnrun.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
Image elements do not have [alt] attributes
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Seejohnrun.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 Seejohnrun.com main page’s claimed encoding is . 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.
seejohnrun.com
Open Graph description is not detected on the main page of See John Run. 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: