2.8 sec in total
680 ms
1.9 sec
238 ms
Click here to check amazing Fan Cons content for United States. Otherwise, check out these important facts you probably never knew about fancons.com
FanCons.com has the best listing of conventions near you with maps, calendars, guests, articles, and much more...
Visit fancons.comWe analyzed Fancons.com page load time and found that the first response time was 680 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
fancons.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value10.8 s
0/100
25%
Value27.7 s
0/100
10%
Value48,630 ms
0/100
30%
Value0.214
58/100
15%
Value61.5 s
0/100
10%
680 ms
71 ms
137 ms
28 ms
27 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Fancons.com, 70% (56 requests) were made to Media.animecons.com and 8% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (680 ms) belongs to the original domain Fancons.com.
Page size can be reduced by 457.9 kB (54%)
851.0 kB
393.0 kB
In fact, the total size of Fancons.com main page is 851.0 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. 45% of websites need less resources to load. Javascripts take 366.9 kB which makes up the majority of the site volume.
Potential reduce by 189.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 189.1 kB or 75% of the original size.
Potential reduce by 1.9 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. Fan Cons images are well optimized though.
Potential reduce by 240.3 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 240.3 kB or 65% of the original size.
Potential reduce by 26.7 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. Fancons.com needs all CSS files to be minified and compressed as it can save up to 26.7 kB or 84% of the original size.
Number of requests can be reduced by 63 (81%)
78
15
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fan Cons. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
fancons.com
680 ms
Ftemplate.css
71 ms
constant.css
137 ms
gpt.js
28 ms
analytics.js
27 ms
tail_header_fancons.gif
203 ms
3XaHtEMc4idW2SbCabrNRA.js
29 ms
search_bg.gif
189 ms
searchButton.gif
187 ms
FanConsCom.png
195 ms
top_menu_tail.gif
190 ms
border.gif
255 ms
corner2_top_left.gif
252 ms
corner2_top_right.gif
253 ms
corner2_bottom_left.gif
254 ms
corner2_bottom_right.gif
254 ms
box2_title.gif
260 ms
box2_corner_left.gif
317 ms
box2_corner_right.gif
318 ms
title_marker.gif
320 ms
border1_top.gif
320 ms
border1_bottom.gif
320 ms
border1_left.gif
326 ms
border1_right.gif
383 ms
corner1_top_left.gif
384 ms
corner1_top_right.gif
385 ms
corner1_bottom_left.gif
386 ms
corner1_bottom_right.gif
386 ms
login_button.gif
392 ms
border3_top.gif
450 ms
border3_bottom.gif
451 ms
corner3_top_left.gif
452 ms
corner3_top_right.gif
453 ms
corner3_bottom_left.gif
454 ms
corner3_bottom_right.gif
493 ms
box3_title.gif
529 ms
box3_corner_left.gif
528 ms
box3_corner_right.gif
529 ms
menu_marker.gif
529 ms
twitter.png
528 ms
googleplus.png
536 ms
facebook.png
601 ms
pubads_impl_82.js
18 ms
collect
44 ms
feedback-tab.png
37 ms
ads
395 ms
container.html
29 ms
tab-right-light-087cbff98d6cd97b87d4a73c4232a642.png
14 ms
tumblr.png
421 ms
pinterest.png
419 ms
youtube.png
419 ms
foursquare.png
417 ms
811-StaffTalkPanelScheduling.jpg
544 ms
border_top.gif
421 ms
border_bottom.gif
419 ms
border_left.gif
420 ms
border_right.gif
420 ms
corner_top_left.gif
417 ms
corner_top_right.gif
479 ms
corner_bottom_left.gif
423 ms
corner_bottom_right.gif
422 ms
box_title.gif
423 ms
box_border_left.gif
423 ms
box_corner_left.gif
485 ms
box_corner_right.gif
480 ms
list_marker.gif
423 ms
tail_footer.gif
422 ms
expansion_embed.js
24 ms
16178143640801471670
59 ms
abg.js
63 ms
m_js_controller.js
81 ms
googlelogo_color_112x36dp.png
43 ms
osd.js
12 ms
favicon
110 ms
nessie_icon_tiamat_white.png
69 ms
s
44 ms
x_button_blue2.png
40 ms
track.js
157 ms
810-ArtistsAlleyPlan2.jpg
200 ms
ui
42 ms
fancons.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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fancons.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
fancons.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 Fancons.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 Fancons.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.
fancons.com
Open Graph description is not detected on the main page of Fan Cons. 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: