7.8 sec in total
663 ms
6.8 sec
264 ms
Click here to check amazing Fail Forum content for China. Otherwise, check out these important facts you probably never knew about failforum.net
HKFF 失敗論壇 - Discuz! Board
Visit failforum.netWe analyzed Failforum.net page load time and found that the first response time was 663 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
failforum.net performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value4.2 s
45/100
25%
Value5.4 s
56/100
10%
Value2,790 ms
3/100
30%
Value0.273
45/100
15%
Value10.0 s
26/100
10%
663 ms
1077 ms
432 ms
657 ms
656 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 36% of them (39 requests) were addressed to the original Failforum.net, 26% (28 requests) were made to Cdn-html.adsfactor.net and 6% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Failforum.net.
Page size can be reduced by 670.9 kB (60%)
1.1 MB
450.3 kB
In fact, the total size of Failforum.net main page is 1.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. 40% of websites need less resources to load. Images take 474.4 kB which makes up the majority of the site volume.
Potential reduce by 52.9 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 13.0 kB, which is 20% 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 52.9 kB or 83% of the original size.
Potential reduce by 175.7 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. Obviously, Fail Forum needs image optimization as it can save up to 175.7 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 289.4 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 289.4 kB or 73% of the original size.
Potential reduce by 152.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. Failforum.net needs all CSS files to be minified and compressed as it can save up to 152.9 kB or 82% of the original size.
Number of requests can be reduced by 56 (55%)
101
45
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fail Forum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
index.php
663 ms
style_7.css
1077 ms
style_7_append.css
432 ms
common.js
657 ms
menu.js
656 ms
ajax.js
874 ms
adsbygoogle.js
24 ms
floatadv.js
424 ms
ga.js
18 ms
logo.gif
427 ms
bkmark.gif
427 ms
menu_bg.gif
428 ms
menu_itemline.gif
428 ms
xml.gif
431 ms
new.gif
452 ms
forum_new.gif
857 ms
forum.gif
865 ms
discuz_icon.gif
868 ms
aids.gif
3086 ms
arrow_right.gif
862 ms
__utm.gif
36 ms
dragon.png
2378 ms
icon01.png
1445 ms
icon02.png
1464 ms
icon03.png
1485 ms
icon04.png
1495 ms
icon06.png
2081 ms
icon07.png
2118 ms
icon08.png
1924 ms
icon09.png
2133 ms
icon11.png
2569 ms
icon12.png
2711 ms
icon13.png
2782 ms
icon14.png
2814 ms
icon16.png
3020 ms
icon17.png
3227 ms
icon19.png
3366 ms
icon21.png
3411 ms
__utm.gif
11 ms
ca-pub-7309525984435511.js
46 ms
zrt_lookup.html
72 ms
show_ads_impl.js
72 ms
adj.php
504 ms
collect
112 ms
like.php
184 ms
ads
180 ms
osd.js
7 ms
vpc6VNjRPXV.js
155 ms
LVx-xkvaJ0b.png
180 ms
1340444018518774426
42 ms
abg.js
44 ms
m_js_controller.js
57 ms
googlelogo_color_112x36dp.png
36 ms
s
17 ms
x_button_blue2.png
17 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
6 ms
lrec.html
86 ms
beacon.js
10 ms
bquery.js
1122 ms
script.js
453 ms
icon20.png
2929 ms
icon22.png
3134 ms
portalbox_bg.gif
2936 ms
__utm.gif
24 ms
__utm.gif
12 ms
ads
302 ms
advclose.gif
3095 ms
__utm.gif
5 ms
edge.6.0.0.min.js
9 ms
lrec_edge.js
9 ms
tag_btm.svg
36 ms
tag_top.svg
37 ms
1.svg
49 ms
2.svg
39 ms
3.svg
40 ms
tv.svg
12 ms
4.svg
21 ms
5.svg
23 ms
6.svg
24 ms
7.svg
25 ms
8.svg
27 ms
mac.svg
28 ms
92.svg
29 ms
tablet.svg
32 ms
10.svg
44 ms
11.svg
39 ms
12.svg
39 ms
13.svg
40 ms
14.svg
41 ms
15.svg
44 ms
16.svg
45 ms
logo.svg
46 ms
lrec_edge.js
42 ms
lrec_edgeActions.js
3 ms
lrec_edgeActions.js
3 ms
150 ms
10e42cd7-b62d-4d80-89d2-15e1de84feaf_728_90.gif
96 ms
ca
84 ms
bb_142x18.png
95 ms
clear.gif
95 ms
cap
29 ms
activeview
15 ms
ca
6 ms
get
4 ms
get
4 ms
new
908 ms
ui
32 ms
failforum.net 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
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
failforum.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
failforum.net 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
BIG5-HKSCS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Failforum.net 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 Failforum.net main page’s claimed encoding is big5-hkscs. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
failforum.net
Open Graph description is not detected on the main page of Fail Forum. 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: