4.1 sec in total
196 ms
3.7 sec
206 ms
Welcome to williambot.com homepage info - get ready to check William Bot best content for United States right away, or after learning these important things about williambot.com
Willbot is an avatar of William Shakespeare, created to commerate 400 years since the great bard hath passed hence.
Visit williambot.comWe analyzed Williambot.com page load time and found that the first response time was 196 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
williambot.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.8 s
55/100
25%
Value8.9 s
15/100
10%
Value16,160 ms
0/100
30%
Value1.015
2/100
15%
Value25.3 s
0/100
10%
196 ms
168 ms
98 ms
164 ms
423 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 45% of them (64 requests) were addressed to the original Williambot.com, 8% (12 requests) were made to 4236808.fls.doubleclick.net and 7% (10 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Williambot.com.
Page size can be reduced by 849.5 kB (11%)
7.7 MB
6.8 MB
In fact, the total size of Williambot.com main page is 7.7 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. 45% of websites need less resources to load. Images take 6.7 MB which makes up the majority of the site volume.
Potential reduce by 18.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 18.2 kB or 72% of the original size.
Potential reduce by 276.3 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. William Bot images are well optimized though.
Potential reduce by 533.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 533.9 kB or 59% of the original size.
Potential reduce by 21.1 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. Williambot.com needs all CSS files to be minified and compressed as it can save up to 21.1 kB or 83% of the original size.
Number of requests can be reduced by 53 (39%)
137
84
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of William Bot. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
williambot.com
196 ms
www.williambot.com
168 ms
98 ms
shakespeare.js
164 ms
conversation-avatar-min.js
423 ms
existor-logo-transparent-arrow.png
153 ms
icon-facebook.png
156 ms
icon-twitter.png
164 ms
icon-google-plus.png
166 ms
blank.gif
225 ms
willbot-logo.jpg
231 ms
icon-willbot.png
237 ms
icon-cleverbot-android.png
239 ms
icon-clevertweet.png
241 ms
icon-clevermessage.png
299 ms
icon-clevernator.png
307 ms
icon-cleverbot.png
317 ms
icon-cleverme.png
319 ms
icon-xaggle.png
321 ms
icon-tyyyp.png
373 ms
icon-botornot.png
380 ms
icon-eviebot.png
397 ms
icon-boibot.png
398 ms
icon-chimbot.png
400 ms
styles-min.css
447 ms
adsbygoogle.js
29 ms
ga.js
20 ms
willbot-logo-transparent-arrow.png
120 ms
eviebot-logo-transparent.png
121 ms
boibot-logo-transparent.png
118 ms
chimbot-logo-transparent.png
118 ms
existor-logo-transparent.png
120 ms
cleverbot-logo-white.png
119 ms
replace-vertical-painting.jpg
153 ms
flag-icons.png
154 ms
quant.js
14 ms
ca-pub-3341468949430013.js
8 ms
zrt_lookup.html
32 ms
show_ads_impl.js
47 ms
__utm.gif
16 ms
pixel;r=113832291;a=p-vPyE9gnSHwUS4;fpan=1;fpa=P0-1224554850-1458448450015;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458448450015;tzo=-180;ref=;url=http%3A%2F%2Fwww.williambot.com%2Fen%2F;ogl=site_name.Willbot%2Ctype.game%2Curl.http%3A%2F%2Fwww%252Ewilliambot%252Ecom%2F%2Cimage.http%3A%2F%2Fwww%252Ewilliambot%252Ecom%2Fimages%2Fwillbot-home-image%252Ejpg%2Ctitle.Willbot%20at%20www%252Ewilliambot%252Ecom%2Cdescription.William%20Shakespeare%20is%20back%20after%20400%20years%252C%20what%20sayeth%20he%3F
9 ms
ads
161 ms
osd.js
10 ms
ads
188 ms
ads
225 ms
89 ms
adj
81 ms
beacon
65 ms
47 ms
adj
53 ms
beacon
35 ms
104 ms
verify_selector.js
187 ms
blank.gif
183 ms
beacon.js
31 ms
bapi
100 ms
154 ms
verify_selector.js
178 ms
blank.gif
175 ms
dt
61 ms
31 ms
dt
28 ms
JLAU00463629.jpg
192 ms
verify_selector.js
35 ms
blank.gif
27 ms
38 ms
dtc
50 ms
dtc
35 ms
verifyr.js
53 ms
verify_selector.js
47 ms
blank.gif
45 ms
bapi
35 ms
APYJ00463631.jpg
180 ms
verifyr.js
67 ms
activityi;src=4236808;type=invmedia;cat=v07FUQdA;ord=-45884177
185 ms
activityi;src=4236808;type=invmedia;cat=jzxoorcy;ord=-45884177
187 ms
activityi;src=4236808;type=invmedia;cat=oofbwwpa;ord=-45884177
186 ms
activityi;src=4236808;type=invmedia;cat=m7kk75gz;ord=-45884177
184 ms
activityi;src=4236808;type=invmedia;cat=fiexoefn;ord=-45884177
182 ms
activityi;src=4236808;type=invmedia;cat=poueoutn;ord=-45884177
186 ms
0
195 ms
verifyr.js
57 ms
activityi;src=4236808;type=invmedia;cat=jzxoorcy;ord=325828575
225 ms
activityi;src=4236808;type=invmedia;cat=poueoutn;ord=325828575
227 ms
dbapi
86 ms
pixel
83 ms
dt
50 ms
lidar.js
37 ms
sbhK2lTE.js
98 ms
dt
57 ms
activityi;src=4236808;type=invmedia;cat=oofbwwpa;ord=325828575
157 ms
activityi;src=4236808;type=invmedia;cat=fiexoefn;ord=325828575
156 ms
activityi;src=4236808;type=invmedia;cat=m7kk75gz;ord=325828575
153 ms
activityi;src=4236808;type=invmedia;cat=v07FUQdA;ord=325828575
149 ms
dbapi
35 ms
pixel
122 ms
pixel
152 ms
dt
27 ms
verifyr.js
58 ms
dt
24 ms
dt
56 ms
cTrvNaRi.html
12 ms
dt
84 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
31 ms
0
55 ms
pixel
57 ms
sd
5 ms
clouds3000-painted.jpg
656 ms
actions.png
83 ms
bg.jpg
151 ms
fset72.jpg
455 ms
fset0.jpg
513 ms
fset73.jpg
427 ms
fset74.jpg
521 ms
fset75.jpg
448 ms
fset76.jpg
679 ms
fset77.jpg
661 ms
fset78.jpg
682 ms
fset79.jpg
727 ms
fset80.jpg
748 ms
fset81.jpg
1006 ms
fset82.jpg
791 ms
fset83.jpg
930 ms
fset84.jpg
827 ms
fset85.jpg
968 ms
fset86.jpg
952 ms
fset87.jpg
944 ms
fset88.jpg
985 ms
fset89.jpg
1202 ms
fset90.jpg
1073 ms
fset91.jpg
1158 ms
fset92.jpg
1241 ms
fset93.jpg
1134 ms
fset94.jpg
1348 ms
fset95.jpg
1255 ms
fset96.jpg
1313 ms
fset97.jpg
1327 ms
fset98.jpg
1423 ms
activeview
12 ms
activeview
19 ms
activeview
19 ms
activeview
21 ms
williambot.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
williambot.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
williambot.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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Williambot.com 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 Williambot.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.
williambot.com
Open Graph data is detected on the main page of William Bot. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: