3.9 sec in total
335 ms
2.8 sec
730 ms
Click here to check amazing Feer content. Otherwise, check out these important facts you probably never knew about feer.com
Breaking news and analysis from the U.S. and around the world at WSJ.com. Politics, Economics, Markets, Life & Arts, and in-depth reporting.
Visit feer.comWe analyzed Feer.com page load time and found that the first response time was 335 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
feer.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value7.9 s
3/100
25%
Value15.2 s
1/100
10%
Value5,080 ms
0/100
30%
Value0
100/100
15%
Value55.3 s
0/100
10%
335 ms
1644 ms
1781 ms
1527 ms
191 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Feer.com, 35% (17 requests) were made to Wsj.com and 14% (7 requests) were made to Images.wsj.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Images.wsj.net.
Page size can be reduced by 4.1 MB (86%)
4.7 MB
647.7 kB
In fact, the total size of Feer.com main page is 4.7 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. 70% of websites need less resources to load. HTML takes 4.5 MB which makes up the majority of the site volume.
Potential reduce by 4.1 MB
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 4.1 MB or 90% of the original size.
Potential reduce by 0 B
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. Feer images are well optimized though.
Potential reduce by 596 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 67 B
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. Feer.com has all CSS files already compressed.
Number of requests can be reduced by 12 (39%)
31
19
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Feer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
feer.com
335 ms
www.wsj.com
1644 ms
video.min.js
1781 ms
audioplayer.min.js
1527 ms
ace.min.js
191 ms
gpt.js
1526 ms
moatheader.js
1669 ms
uac.min.1.0.44.js
515 ms
djcmp.min.1.0.26.js
1404 ms
21259101085
1778 ms
cxense-candy.js
1524 ms
wsj-logo-big-black.165e51cc.svg
1580 ms
im-635597
1636 ms
BN-SE117_STERN__A_20170219231355.jpg
1490 ms
BN-CW279_mims_A_20140520065912.jpg
1713 ms
BN-SZ646_SAUNDE_A_20170417174700.jpg
1957 ms
im-636194
1723 ms
im-635870
1961 ms
im-636001
1961 ms
im-635191
1960 ms
im-631628
1960 ms
im-635632
1960 ms
Retina-Book.woff
1376 ms
Retina-Medium.woff
1376 ms
Retina-Light.woff
1530 ms
RetinaNarr-Book.woff
664 ms
RetinaNarr-Medium.woff
737 ms
RetinaNarr-Light.woff
734 ms
RetinaNarr-Bold.woff
805 ms
Escrow+Display+Condensed+Bold.woff
735 ms
Escrow+Display+Condensed+Roman.woff
913 ms
Exchange-Book.woff
925 ms
Exchange-Medium.woff
924 ms
Exchange-BookItalic.woff
925 ms
Exchange-MediumItalic.woff
925 ms
runtime.0f1db677687aea.js
390 ms
vendors.d2858507c4db3e.js
632 ms
main.3e1345bbb5e61a.js
637 ms
sso-auth.js
637 ms
video.min.css
368 ms
audioplayer.min.css
373 ms
wrapperMessagingWithoutDetection.js
585 ms
pubads_impl_2022092701.js
501 ms
ppub_config
497 ms
v2
238 ms
n.js
225 ms
n.js
226 ms
iframe.html
131 ms
wrapperMessagingWithoutDetection.js
144 ms
feer.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.
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 IDs are not unique
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
Links do not have a discernible name
feer.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
feer.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feer.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 Feer.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.
feer.com
Open Graph data is detected on the main page of Feer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: