1.4 sec in total
202 ms
840 ms
340 ms
Welcome to api.facebook.com homepage info - get ready to check Api Facebook best content for United States right away, or after learning these important things about api.facebook.com
Code to connect people with Facebook for Developers. Explore AI, business tools, gaming, open source, publishing, social hardware, social integration, and virtual reality. Learn about Facebook’s globa...
Visit api.facebook.comWe analyzed Api.facebook.com page load time and found that the first response time was 202 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
api.facebook.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value6.3 s
10/100
25%
Value6.0 s
46/100
10%
Value1,470 ms
14/100
30%
Value1.001
2/100
15%
Value15.8 s
6/100
10%
202 ms
39 ms
261 ms
46 ms
76 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Api.facebook.com, 27% (17 requests) were made to Facebook.com and 17% (11 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (281 ms) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 86.2 kB (12%)
748.4 kB
662.2 kB
In fact, the total size of Api.facebook.com main page is 748.4 kB. 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 672.6 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.4 kB or 74% of the original size.
Potential reduce by 45.8 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. Api Facebook images are well optimized though.
Potential reduce by 50 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.
Number of requests can be reduced by 39 (72%)
54
15
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Api Facebook. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
developers.facebook.com
202 ms
fbevents.js
39 ms
tr
261 ms
N5JKrwrFRBP.css
46 ms
410ucuAGgaJ.css
76 ms
5VZ003vMUZg.css
59 ms
hzAbnp0y84k.css
85 ms
pERLJfhzcxv.css
79 ms
q68gy-v_YMF.js
89 ms
12056999_527586047417155_1427094715_n.jpg
202 ms
12056942_504542496383313_589124126_n.png
216 ms
12056974_1139692222715512_2137855326_n.png
262 ms
12057195_850865451695022_1842957663_n.png
260 ms
12057222_917248651693816_519438459_n.png
264 ms
12057004_982192548504015_1573584927_n.png
279 ms
12624062_876790125771359_1683950322_n.jpg
281 ms
12056981_500844813416602_1022231969_n.png
281 ms
11891357_1061720347212845_584378441_n.png
281 ms
11891349_532301260256232_831298041_n.png
281 ms
12056959_495734753934070_457844252_n.png
281 ms
270 ms
269 ms
269 ms
251 ms
css;base64,
9 ms
EoarYgA68t4.css
58 ms
UmiOWJT548a.css
68 ms
AeVtnX55bMN.png
66 ms
157 ms
239 ms
246 ms
246 ms
246 ms
245 ms
244 ms
247 ms
248 ms
249 ms
248 ms
248 ms
8AIaACgBqQAkAhYALQHJAEYCwQBaAAAAAAIbACU=
25 ms
A9sayBn2IEF.otf
84 ms
xA32tpmseVi.otf
105 ms
M0ebpfLaTZg.otf
102 ms
Kg3pu66YGCS.otf
104 ms
p9LHntgACi6.otf
104 ms
_4VXT2T370W.otf
118 ms
fb4d_logo-2x.png
67 ms
analytics.js
63 ms
VjkrC3Nlo2e.js
77 ms
FJmpeSpHpjS.js
76 ms
1FCa-btixu2.js
72 ms
Oagsvfb4VWi.js
76 ms
pQrUxxo5oQp.js
75 ms
LTv6ZK-5zxz.js
141 ms
rw3bEcylZVO.js
141 ms
1bNoFZUdlYZ.js
141 ms
_UYztdBNTjs.js
75 ms
7BE0CZr3HTs.js
147 ms
H3EKDTObx05.js
75 ms
Q4A0UyjU8W2.js
145 ms
Y9mSXzUZWFV.js
147 ms
4c7U2CSBOsL.js
148 ms
api.facebook.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
Links do not have a discernible name
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.
api.facebook.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
api.facebook.com 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.facebook.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 Api.facebook.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.
api.facebook.com
Open Graph data is detected on the main page of Api Facebook. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: