4.2 sec in total
331 ms
3.2 sec
723 ms
Click here to check amazing FAKEOFF content for Ukraine. Otherwise, check out these important facts you probably never knew about fakeoff.org
Инсайды, слухи, предположения, мнения, расследования, мифы, легенды, разоблачения и многое другое
Visit fakeoff.orgWe analyzed Fakeoff.org page load time and found that the first response time was 331 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 65% of websites can load faster.
fakeoff.org performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value9.5 s
0/100
25%
Value9.2 s
13/100
10%
Value880 ms
32/100
30%
Value0.28
43/100
15%
Value18.4 s
3/100
10%
331 ms
227 ms
318 ms
153 ms
152 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 59% of them (82 requests) were addressed to the original Fakeoff.org, 10% (14 requests) were made to Ulogin.ru and 5% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (833 ms) relates to the external source Ulogin.ru.
Page size can be reduced by 784.4 kB (38%)
2.1 MB
1.3 MB
In fact, the total size of Fakeoff.org main page is 2.1 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. 75% 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 939.6 kB which makes up the majority of the site volume.
Potential reduce by 56.4 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 56.4 kB or 78% of the original size.
Potential reduce by 22.2 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. FAKEOFF images are well optimized though.
Potential reduce by 455.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 455.9 kB or 60% of the original size.
Potential reduce by 249.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. Fakeoff.org needs all CSS files to be minified and compressed as it can save up to 249.9 kB or 84% of the original size.
Number of requests can be reduced by 58 (52%)
111
53
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FAKEOFF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
fakeoff.org
331 ms
font-awesome.min.css
227 ms
bootstrap.min.css
318 ms
add-columns.css
153 ms
add-ons.css
152 ms
style.css
303 ms
color1.css
162 ms
animate.css
378 ms
ulogin.js
460 ms
jquery-2.1.4.min.js
377 ms
common.js
167 ms
lang.js
226 ms
translations.js
568 ms
form.js
301 ms
jquery.ba-throttle-debounce.min.js
304 ms
responsive.js
320 ms
bootstrap.min.js
451 ms
jquery.easing.js
377 ms
matchMedia.js
379 ms
jquery-waypoints.js
399 ms
jquery.flexslider.js
450 ms
jquery.transit.js
451 ms
jquery.leanModal.min.js
453 ms
jquery.doubletaptogo.js
479 ms
jquery.ba-throttle-debounce.min.js
524 ms
smoothscroll.js
524 ms
main.js
524 ms
adsbygoogle.js
6 ms
flexslider.css
306 ms
mCustomScrollbar.css
337 ms
shortcodes.css
376 ms
css
24 ms
logo-40x40.png
113 ms
loading.gif
111 ms
3403d20436925dc7.jpeg
109 ms
a0454813e9e02bfb.jpeg
147 ms
ea957af63a4b7815.jpeg
112 ms
c59180f845ff83cf.jpg
112 ms
4dc58b27f4351672.jpg
189 ms
9b9950954b307c9d.jpg
190 ms
037fc00863ed1618.jpg
189 ms
1ed1cdc1ebaa88ef.jpeg
190 ms
e28565e9d23b7215.jpeg
190 ms
7bc3358920a4426f.jpeg
191 ms
prolab-biz-336x280.jpg
330 ms
0eC6fl06luXEYWpBSJvXCKCWcynf_cDxXwCLxiixG1c.ttf
43 ms
oeEVQYYBjVpg-nn8NItjTw.ttf
76 ms
ZLqKeelYbATG60EpZBSDy6CWcynf_cDxXwCLxiixG1c.ttf
77 ms
77FXFjRbGzN4aCrSFhlh3qCWcynf_cDxXwCLxiixG1c.ttf
76 ms
fontawesome-webfont.woff
274 ms
3403d20436925dc7.jpeg
232 ms
ea957af63a4b7815.jpeg
232 ms
c59180f845ff83cf.jpg
231 ms
SourceSansPro-Bold.woff
331 ms
hit
295 ms
a0454813e9e02bfb.jpeg
200 ms
4dc58b27f4351672.jpg
158 ms
037fc00863ed1618.jpg
159 ms
9b9950954b307c9d.jpg
159 ms
1ed1cdc1ebaa88ef.jpeg
246 ms
e28565e9d23b7215.jpeg
246 ms
7bc3358920a4426f.jpeg
246 ms
analytics.js
118 ms
watch.js
218 ms
fbds.js
113 ms
fd189f8e567e01af.jpeg
112 ms
71add3f34a5a7565.jpeg
112 ms
eb21cbdb399c7083.jpeg
253 ms
1181213117a1eeef.jpeg
149 ms
12d36be854f9a70c.jpeg
149 ms
65c8c908c5c2c2b2.jpg
229 ms
c7e35731902a919d.jpg
227 ms
84f3a0a5c3cafd4a.jpg
229 ms
dfe6ee1a4ab81498.jpg
252 ms
4c0b1660e2dc1f01.jpg
251 ms
f97ed2a310c5e1df.jpg
255 ms
afebe0701831a087.jpg
289 ms
423b6bf5dccb8627.png
288 ms
655f76044ab449d9.jpg
319 ms
e45e76607ca73258.jpg
316 ms
0f85efe04060460f.jpg
317 ms
5451d45c8376d1e1.jpg
322 ms
46d33d0f5a87db3f.jpg
367 ms
ccdc0fe200ad575d.jpg
368 ms
0b1f25286f76b175.jpeg
404 ms
c2d40e4ae6250bda.jpg
402 ms
bf83453ee053ac78.jpg
403 ms
2945efac04608790.jpg
407 ms
657036dffa505f18.jpg
496 ms
56fe49e3e7990052.jpg
496 ms
63e90b78e0380286.png
530 ms
064825b02241bda8.png
527 ms
eeed07de4ee59c28.jpeg
527 ms
match
210 ms
blank.gif
812 ms
link.png
833 ms
ca-pub-2093309234994562.js
86 ms
zrt_lookup.html
151 ms
show_ads_impl.js
80 ms
collect
49 ms
03.png
267 ms
hit
149 ms
watch.js
511 ms
stats.html
812 ms
drop.html
816 ms
collect
109 ms
ads
178 ms
161 ms
osd.js
26 ms
ads
185 ms
css
67 ms
m_js_controller.js
37 ms
abg.js
49 ms
css
77 ms
nessie_icon_thin_arrow_big_white.png
66 ms
s
55 ms
googlelogo_color_112x36dp.png
63 ms
x_button_blue2.png
43 ms
favicon
107 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
5 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
78 ms
advert.gif
85 ms
RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf
30 ms
1
86 ms
ui
38 ms
easyXDM.min.js
165 ms
stats.js
157 ms
iscroll.5.js
167 ms
lang.js
158 ms
drop.js
309 ms
hit
542 ms
hit
521 ms
bga.png
156 ms
small.png
308 ms
hit
137 ms
activeview
14 ms
activeview
21 ms
hit
134 ms
fakeoff.org 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
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
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.
fakeoff.org 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fakeoff.org 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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fakeoff.org can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Fakeoff.org 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.
fakeoff.org
Open Graph data is detected on the main page of FAKEOFF. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: