13.3 sec in total
1.3 sec
10.8 sec
1.2 sec
Welcome to fandomobsessed.com homepage info - get ready to check Fandomobsessed best content for United States right away, or after learning these important things about fandomobsessed.com
This website is for sale! fandomobsessed.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, fandomobses...
Visit fandomobsessed.comWe analyzed Fandomobsessed.com page load time and found that the first response time was 1.3 sec and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fandomobsessed.com performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value1.7 s
99/100
25%
Value4.1 s
80/100
10%
Value1,980 ms
8/100
30%
Value0.143
78/100
15%
Value5.3 s
73/100
10%
1291 ms
579 ms
371 ms
370 ms
550 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 44% of them (67 requests) were addressed to the original Fandomobsessed.com, 21% (32 requests) were made to Static.xx.fbcdn.net and 10% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (7.2 sec) belongs to the original domain Fandomobsessed.com.
Page size can be reduced by 361.2 kB (19%)
1.9 MB
1.6 MB
In fact, the total size of Fandomobsessed.com main page is 1.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 78.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. This page needs HTML code to be minified as it can gain 17.1 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 78.2 kB or 84% of the original size.
Potential reduce by 44.0 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. Fandomobsessed images are well optimized though.
Potential reduce by 130.0 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 130.0 kB or 46% of the original size.
Potential reduce by 108.9 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. Fandomobsessed.com needs all CSS files to be minified and compressed as it can save up to 108.9 kB or 83% of the original size.
Number of requests can be reduced by 76 (54%)
141
65
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fandomobsessed. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
fandomobsessed.com
1291 ms
css.php
579 ms
style.css
371 ms
tp_twitter_plugin.css
370 ms
symple_shortcodes_styles.css
550 ms
style.css
738 ms
font-awesome.min.css
526 ms
css
26 ms
responsive.css
548 ms
jquery.js
1475 ms
marquee.js
702 ms
innerfade.js
906 ms
tie.js
730 ms
adsbygoogle.js
5 ms
widgets.js
87 ms
jpanel-menu.js
625 ms
images-loaded.js
533 ms
fitvids.js
567 ms
magnific-popup.js
756 ms
global.js
709 ms
non-mobile.js
740 ms
flexslider.js
965 ms
flexslider-home.js
821 ms
bxslider.js
1061 ms
equal-heights.js
920 ms
posts-carousel-init.js
937 ms
flexslider-featured-posts.js
999 ms
LqlY4oLe_normal.png
43 ms
logo-fo.png
259 ms
twitter.png
259 ms
facebook.png
261 ms
tumblr.png
260 ms
pinterest.png
263 ms
youtube.png
259 ms
instagram.png
387 ms
IMG_2429-630x390.jpg
964 ms
IMG_24121.jpg
1373 ms
Cinderella-630x390.jpg
805 ms
Poldark_epi2_5-630x390.jpg
798 ms
luke-evans-gaston-disney.jpg
1324 ms
OutlanderTrailer-630x390.jpg
837 ms
tumblr_nfnfdc4WwV1r5abf1o6_500.gif
7234 ms
black_jack_randall-300x190.jpg
983 ms
IMG_2429-300x190.jpg
1013 ms
IMG_24121-300x190.jpg
1087 ms
Zoolander2-300x190.jpg
1190 ms
beauty-and-the-beast-300x190.jpg
1196 ms
paul_rudd_07.jpg
1264 ms
ant-man-620x320.png
2171 ms
Jurassic_World-620x320.jpg
1776 ms
Stanley-Weber16-620x320.jpg
1651 ms
laurence-dobiesz1.jpg
1516 ms
mockingjay-part2-620x320.jpg
1726 ms
RAYMOND2.jpg
1699 ms
OutlanderNewTrailer08-620x320.jpg
2006 ms
zoella-620x320.jpg
2068 ms
OutlanderTeaser1-620x320.jpg
1909 ms
twitter-bird-3.png
1951 ms
ant-man-300x295.png
2676 ms
Jurassic_World-300x295.jpg
2303 ms
Stanley-Weber16-300x295.jpg
2183 ms
laurence-dobiesz1-300x295.jpg
2249 ms
analytics.js
29 ms
nav-divider.png
2318 ms
lupa.png
2333 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
63 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
62 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
65 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
64 ms
RJMlAoFXXQEzZoMSUteGWKCWcynf_cDxXwCLxiixG1c.ttf
61 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
63 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
65 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
64 ms
PKCRbVvRfd5n7BTjtGiFZC3USBnSvpkopQaUR-2r7iU.ttf
63 ms
collect
30 ms
ca-pub-5798157789048306.js
152 ms
zrt_lookup.html
139 ms
show_ads_impl.js
53 ms
fontawesome-webfont.woff
2199 ms
home-flex-loader.gif
2251 ms
carousel-overlay.png
2302 ms
post-entry-link-plus.png
2300 ms
arrow-right.png
2379 ms
all.js
124 ms
adsbygoogle.js
99 ms
ads
219 ms
ads
246 ms
ads
260 ms
224 ms
xd_arbiter.php
26 ms
xd_arbiter.php
43 ms
m_js_controller.js
30 ms
abg.js
57 ms
favicon
123 ms
googlelogo_color_112x36dp.png
90 ms
nessie_icon_tiamat_white.png
50 ms
s
58 ms
x_button_blue2.png
41 ms
30050-220478-36959-10
147 ms
favicon
11 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
21 ms
IMM_Roku_3142016_AWS_Display_Q1_16_Roku-HBO_Watch-Sesame_x_x_v1_RK0000345_300x600.jpg
35 ms
ping
57 ms
white-plus.png
193 ms
gray-clock.png
198 ms
like_box.php
263 ms
ui
33 ms
410ucuAGgaJ.css
81 ms
tSbl8xBI27R.css
75 ms
Czh0gDTFcBt.css
86 ms
Ek6lpayKeeB.css
112 ms
EoarYgA68t4.css
98 ms
5VZ003vMUZg.css
140 ms
dAhyk4_vXRy.css
136 ms
q68gy-v_YMF.js
133 ms
FJmpeSpHpjS.js
222 ms
0wM5s1Khldu.js
246 ms
1bNoFZUdlYZ.js
248 ms
njO1TPvGzoR.js
256 ms
1QuX41zDRrx.js
255 ms
Oagsvfb4VWi.js
259 ms
LTv6ZK-5zxz.js
266 ms
1FCa-btixu2.js
293 ms
IjqSyiwKeaX.js
264 ms
rBxSIHk4zIe.js
308 ms
n6VgtouijQL.js
320 ms
7BE0CZr3HTs.js
291 ms
pQrUxxo5oQp.js
319 ms
_UYztdBNTjs.js
345 ms
-7JBD_ybv4q.js
350 ms
Kt4tkgSRvHH.js
349 ms
971067_653301878028281_1214561986_n.png
266 ms
1001711_653324394692696_537508948_n.jpg
245 ms
12814598_973314272746705_2110560452107106916_n.jpg
240 ms
12239578_1070749946291751_5062839412704311502_n.jpg
239 ms
11781693_1480392628939038_9091131457439871650_n.jpg
247 ms
10307226_807772735993256_1542154584650032744_n.jpg
246 ms
12745620_1114339351911059_8775395391742539457_n.jpg
243 ms
11796272_10152901050366640_7660836141049111545_n.jpg
260 ms
12243397_10156265995840080_6531794176964467034_n.jpg
243 ms
12402411_1013665592025983_211735741_n.jpg
258 ms
12662443_1007278332664709_623279466880490597_n.jpg
261 ms
11108199_882842438441633_5853684496542566725_n.jpg
259 ms
11149571_882842478441629_1314895489742672118_n.jpg
257 ms
17122_853993284659882_458179956349317616_n.jpg
261 ms
11102757_852898078102736_4234698148003709887_n.jpg
257 ms
wL6VQj7Ab77.png
230 ms
s7jcwEQH7Sx.png
226 ms
l5aPruN9xMM.png
227 ms
QDwYpIaRyfG.png
227 ms
K00K-UgnsKu.png
228 ms
b8XhdWI9eAN.js
102 ms
K_65vAc89SX.png
83 ms
I6-MnjEovm5.js
15 ms
fandomobsessed.com accessibility score
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
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.
fandomobsessed.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
fandomobsessed.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fandomobsessed.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 Fandomobsessed.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.
fandomobsessed.com
Open Graph description is not detected on the main page of Fandomobsessed. 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: