13.4 sec in total
2.5 sec
10.6 sec
400 ms
Welcome to wittysam.com homepage info - get ready to check Witty Sam best content right away, or after learning these important things about wittysam.com
I had the weirdest dream last night that bordered on a nightmare... except for one thing. This will reveal itself at the end.
Visit wittysam.comWe analyzed Wittysam.com page load time and found that the first response time was 2.5 sec and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
wittysam.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value5.1 s
25/100
25%
Value7.1 s
31/100
10%
Value190 ms
90/100
30%
Value0.101
89/100
15%
Value5.6 s
69/100
10%
2471 ms
470 ms
493 ms
565 ms
1013 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 42% of them (33 requests) were addressed to the original Wittysam.com, 37% (29 requests) were made to Scontent.xx.fbcdn.net and 6% (5 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Badge.facebook.com.
Page size can be reduced by 243.5 kB (20%)
1.2 MB
976.0 kB
In fact, the total size of Wittysam.com main page is 1.2 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. 35% of websites need less resources to load. Images take 871.9 kB which makes up the majority of the site volume.
Potential reduce by 33.1 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 33.1 kB or 72% of the original size.
Potential reduce by 26.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. Witty Sam images are well optimized though.
Potential reduce by 151.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 151.1 kB or 64% of the original size.
Potential reduce by 32.8 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. Wittysam.com needs all CSS files to be minified and compressed as it can save up to 32.8 kB or 50% of the original size.
Number of requests can be reduced by 26 (34%)
76
50
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Witty Sam. 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 from 7 to 1 for CSS and as a result speed up the page load time.
www.wittysam.com
2471 ms
style.css
470 ms
avatars.css
493 ms
imgareaselect.css
565 ms
dashicons.min.css
1013 ms
thickbox.css
579 ms
styles.css
502 ms
commentluv.css
505 ms
jquery.js
1216 ms
jquery-migrate.min.js
744 ms
commentluv.js
752 ms
diggthis.js
162 ms
getnetworkwidget
80 ms
friendconnect.js
26 ms
wittysam
65 ms
jquery.imgareaselect.min.js
571 ms
thickbox.js
598 ms
jquery.form.min.js
1018 ms
scripts.js
794 ms
wp-embed.min.js
832 ms
wp-emoji-release.min.js
1084 ms
blog.friendfeed.com
74 ms
logo_small.png
26 ms
786729961.1423.2091182535.png
4735 ms
STB-6.png
308 ms
bg.gif
307 ms
rssbig.gif
308 ms
bg-portrait7.jpg
531 ms
date.png
307 ms
the-perfect-ghost.jpg
307 ms
thewittysam-sign1.jpg
366 ms
image.jpg
1954 ms
kerri-anne-kennerley-THE-ONE.jpg
1495 ms
thewittysam-sign1.jpg
559 ms
post.png
549 ms
packaged.png
615 ms
search.png
720 ms
bg-footer.gif
731 ms
rss.png
732 ms
ifr
370 ms
ga.js
41 ms
__utm.gif
19 ms
loadingAnimation.gif
566 ms
closeit.png
705 ms
getnetworkwidgetmain
143 ms
12803011_10154092433966414_5353762163501953405_n.jpg
77 ms
10562965_849832041708154_6710319905668386424_n.jpg
62 ms
12096095_10207138001557409_6769120719795827840_n.jpg
68 ms
60402_1596588882695_6181446_n.jpg
82 ms
12642722_10153452495032399_7161558233762864980_n.jpg
78 ms
12821603_10208952798355805_7808975079308682921_n.jpg
85 ms
247649_10150193547981174_2830437_n.jpg
84 ms
12821428_10153591404627736_2289550103870899243_n.jpg
87 ms
12219618_10208583551572574_7455564878520472222_n.jpg
90 ms
UlIqmHJn-SK.gif
91 ms
537271_10201165272386987_731216943_n.jpg
89 ms
37125_160793577273375_6931516_n.jpg
84 ms
11902592_10153471931619123_8153250750034565177_n.jpg
96 ms
UlIqmHJn-SK.gif
95 ms
76964_448508482953_5122520_n.jpg
64 ms
10514531_10204319415209827_5191630435813784759_n.jpg
75 ms
32610_3983815008910_434729117_n.jpg
74 ms
1499664_10202039477641234_1008535111_n.jpg
70 ms
1656154_10202303090832479_947500026_n.jpg
69 ms
11540906_10153214944711645_2112297451853604084_n.jpg
55 ms
UlIqmHJn-SK.gif
53 ms
527353_10150647318871662_722467108_n.jpg
52 ms
197505_10150115356512406_1429545_n.jpg
60 ms
UlIqmHJn-SK.gif
40 ms
28339_1428111071688_4593711_n.jpg
32 ms
12274618_10153811119979962_4632929601418981716_n.jpg
32 ms
12715762_10154041332307216_7552627133369574423_n.jpg
31 ms
UlIqmHJn-SK.gif
29 ms
12342435_10154424717183626_468046064517148301_n.jpg
19 ms
12507169_10153356094132467_5258035170502849361_n.jpg
17 ms
12662042_10153552042572950_6726224791939783043_n.jpg
16 ms
1960044_10201587946362141_1184912637_n.jpg
17 ms
12651246_10156491774355183_919600353100181342_n.jpg
15 ms
180089_141770972550903_982215_n.jpg
15 ms
wittysam.com accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
wittysam.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
Issues were logged in the Issues panel in Chrome Devtools
wittysam.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wittysam.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 Wittysam.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.
wittysam.com
Open Graph description is not detected on the main page of Witty Sam. 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: