62 sec in total
9.4 sec
51.6 sec
1 sec
Welcome to fandom.id homepage info - get ready to check Fandom best content for Indonesia right away, or after learning these important things about fandom.id
Karena sepakbola tidak selesai setelah 90 menit.
Visit fandom.idWe analyzed Fandom.id page load time and found that the first response time was 9.4 sec and then it took 52.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 24 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fandom.id performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value25.3 s
0/100
25%
Value21.7 s
0/100
10%
Value3,860 ms
1/100
30%
Value0.126
83/100
15%
Value21.3 s
1/100
10%
9387 ms
65 ms
2794 ms
644 ms
642 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 58% of them (88 requests) were addressed to the original Fandom.id, 4% (6 requests) were made to Dsum-sec.casalemedia.com and 4% (6 requests) were made to Px.owneriq.net. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Fandom.id.
Page size can be reduced by 2.5 MB (64%)
3.9 MB
1.4 MB
In fact, the total size of Fandom.id main page is 3.9 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. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 266.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 266.1 kB or 89% of the original size.
Potential reduce by 42.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. Fandom images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 72% of the original size.
Potential reduce by 1.0 MB
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. Fandom.id needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 89% of the original size.
Number of requests can be reduced by 91 (81%)
112
21
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fandom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
fandom.id
9387 ms
shareaholic.js
65 ms
wp-emoji-release.min.js
2794 ms
styles.css
644 ms
disqus_rcw.css
642 ms
settings.css
649 ms
css
53 ms
css
85 ms
css
112 ms
bwg_frontend.css
650 ms
sumoselect.css
1298 ms
font-awesome.css
1304 ms
jquery.mCustomScrollbar.css
1294 ms
style.php
8030 ms
woocommerce-layout.css
1865 ms
woocommerce.css
1868 ms
foundation.min.css
1888 ms
font-awesome.min.css
2362 ms
app.css
2711 ms
style.css
2379 ms
wpp.css
2554 ms
widget.css
2895 ms
default.min.css
2895 ms
js_composer.min.css
3903 ms
custom.css
3273 ms
shortcode.css
4195 ms
woocommerce-pos.css
4715 ms
jetpack.css
7384 ms
jquery.js
10810 ms
jquery-migrate.min.js
8017 ms
lightbox.js
7278 ms
jquery.themepunch.tools.min.js
19897 ms
jquery.themepunch.essential.min.js
16420 ms
bwg_frontend.js
7998 ms
jquery.sumoselect.min.js
10661 ms
jquery.mobile.js
8755 ms
jquery.mCustomScrollbar.concat.min.js
9306 ms
jquery.fullscreen-0.4.1.js
9329 ms
bwg_gallery_box.js
9972 ms
add-to-cart.min.js
9994 ms
css
96 ms
css
94 ms
5b00a1d7a8f3653d45ca9dbb3ba3bd7f.json
112 ms
woocommerce-add-to-cart.js
10020 ms
jquery.form.min.js
9290 ms
scripts.js
11354 ms
jquery.blockUI.min.js
12968 ms
woocommerce.min.js
9863 ms
jquery.cookie.min.js
10394 ms
cart-fragments.min.js
10395 ms
devicepx-jetpack.js
52 ms
gprofiles.js
97 ms
wpgroho.js
11062 ms
vendor.min.js
20094 ms
app.min.js
11673 ms
e-201614.js
52 ms
wp-embed.min.js
20091 ms
js_composer_front.min.js
12247 ms
style.css
12961 ms
count.js
12971 ms
fandom-logo-white.png
970 ms
fandom-logo-color.png
2110 ms
johan-cruyff-ruang-waktu.jpg
15140 ms
blog-england_2763696a.jpg
19945 ms
luciano.png
14773 ms
Juve1.jpg
19945 ms
choirul-huda-persela-lamongan_15nvcupultt9r1idxhmvwse8io-670x450.jpg
3810 ms
soetjipto-soentoro-fandom-670x450.png
11182 ms
payet-670x450.jpg
9410 ms
Cristian-Gonzales-670x450.jpg
13271 ms
WidodoCPutra-HelmiFithriansyah-670x450.jpg
13049 ms
johan-Ahmad-Alfarizi-Arema-670x450.jpg
15133 ms
hendro-siswanto-570x300.jpg
14792 ms
Benzema-280x150.jpg
15691 ms
liverpool-dortmund-280x150.jpg
15713 ms
vardy-kane.jpg
16843 ms
rashford.jpg
19938 ms
Imam-Nahrawi-Belum-Mau-Cabut-Pembekuan-PSSI.jpg
19938 ms
1280px-Ajax_puchar.jpg
19939 ms
football-manager-2016-720jpg-32cad9_1280w.jpg
19938 ms
Ossett-FC-DVC-Football-Academy.jpg
19938 ms
solar-eclipse-fandom.jpg
19938 ms
choirul-huda-persela-lamongan_15nvcupultt9r1idxhmvwse8io-388x308.jpg
19938 ms
soetjipto-soentoro-fandom-388x308.png
19939 ms
payet.jpg
19940 ms
Cristian-Gonzales-388x308.jpg
19939 ms
WidodoCPutra-HelmiFithriansyah-388x308.jpg
19940 ms
kejam.jpg
19943 ms
Chevrolet-Fan-Cup-1.jpg
19943 ms
posterIS-1.jpg
19945 ms
Poster-Pasoepati-Campus.jpg_large-1.jpeg
19945 ms
buku-sepakbola20-400x150.png
19945 ms
analytics.js
94 ms
shrMain.min.js
365 ms
collect
60 ms
1bHRUMxmJHoup12DnI9XmQ.woff
139 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
357 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
352 ms
fontawesome-webfont.woff
20487 ms
fontawesome-webfont.woff
20488 ms
RBnwCWfuc-HyYSgdK3uw-_esZW2xOQ-xsNqO47m55DA.woff
352 ms
QABk9IxT-LFTJ_dQzv7xpNIh4imgI8P11RFo6YPCPC0.woff
351 ms
jquery.min.js
118 ms
pageview.gif
266 ms
count.js
557 ms
fandom.id
19613 ms
hovercard.css
116 ms
services.css
113 ms
vglnk.js
125 ms
partners.js
191 ms
g.gif
112 ms
pixel.gif
94 ms
pixel.gif
94 ms
ih6et8.js
158 ms
usermatch
472 ms
beacon.js
87 ms
cms-sh2c.html
138 ms
ping_match.gif
250 ms
eexelate.js
241 ms
287 ms
2964
89 ms
ep
108 ms
ping
75 ms
ep
226 ms
usermatch
247 ms
pixel
229 ms
rs
211 ms
238 ms
pixel
63 ms
domains
238 ms
VwgRksAoJV8AAfnTJ1sAAACJ%26636
524 ms
i.gif
580 ms
net.php
166 ms
pixel
260 ms
match-result
211 ms
pixel
124 ms
generic
62 ms
crum
400 ms
cfcm.ashx
65 ms
rum
410 ms
m
1216 ms
rum
327 ms
pixel.gif
168 ms
rum
336 ms
rum
361 ms
ermcm
174 ms
52154.gif
84 ms
pixel.gif
121 ms
xrefid.xgi
47 ms
crum
77 ms
fontawesome-webfont.ttf
2834 ms
fontawesome-webfont.ttf
2235 ms
woocommerce-smallscreen.css
300 ms
fandom.id 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-hidden="true"] elements contain focusable descendents
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
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.
fandom.id 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fandom.id SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ID
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fandom.id can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed English language. Our system also found out that Fandom.id 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.
fandom.id
Open Graph data is detected on the main page of Fandom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: