5.1 sec in total
1.1 sec
3.9 sec
162 ms
Visit faa.ro now to see the best up-to-date Faa content for Romania and also check out these interesting facts you probably never knew about faa.ro
FAA, Facultatea de Administratie si Afaceri, Universitatea din Bucuresti, Specializarea Marketing, Administrarea Afacerilor, Administratie Publica, Cibernetica Economica
Visit faa.roWe analyzed Faa.ro page load time and found that the first response time was 1.1 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
faa.ro performance score
name
value
score
weighting
Value14.6 s
0/100
10%
Value35.0 s
0/100
25%
Value17.4 s
0/100
10%
Value290 ms
80/100
30%
Value0.324
35/100
15%
Value18.9 s
3/100
10%
1108 ms
375 ms
235 ms
243 ms
245 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 70% of them (64 requests) were addressed to the original Faa.ro, 11% (10 requests) were made to Static.xx.fbcdn.net and 5% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Faa.ro.
Page size can be reduced by 430.5 kB (65%)
662.8 kB
232.3 kB
In fact, the total size of Faa.ro main page is 662.8 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. 45% of websites need less resources to load. Images take 349.0 kB which makes up the majority of the site volume.
Potential reduce by 49.0 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 49.0 kB or 80% of the original size.
Potential reduce by 234.3 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, Faa needs image optimization as it can save up to 234.3 kB or 67% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 87.3 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 87.3 kB or 48% of the original size.
Potential reduce by 59.8 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. Faa.ro needs all CSS files to be minified and compressed as it can save up to 59.8 kB or 84% of the original size.
Number of requests can be reduced by 50 (57%)
87
37
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
faa.ro
1108 ms
typography2.php
375 ms
sigplus.min.css
235 ms
boxplus.min.css
243 ms
boxplus.lightsquare.css
245 ms
boxplus.transition.css
246 ms
moo_maximenuhck.css
469 ms
maximenuhck.php
596 ms
beez_20_beez5-position12.css
484 ms
maximenuck.css
487 ms
mootools-core.js
844 ms
core.js
611 ms
caption.js
705 ms
jsapi
14 ms
jquery.include.min.js
718 ms
jquery.noconflict.js
725 ms
boxplus.min.js
827 ms
boxplus.lang.min.js
842 ms
boxplus.transition.min.js
943 ms
template.css
1065 ms
blue.css
975 ms
trafic.js
254 ms
jquery.min.js
30 ms
all.js
7 ms
132 ms
ga.js
44 ms
page_bg.png
119 ms
en.jpg
122 ms
faa.png
959 ms
topmenu_left1.png
237 ms
topmenu_right1.png
238 ms
topmenu_bg1.png
244 ms
drop.gif
362 ms
drop-right.gif
366 ms
left_border.png
478 ms
right_border.png
483 ms
moduletable_bg.gif
481 ms
moduletable_bottom.png
607 ms
moduletable_top.gif
607 ms
moduletable_h3.png
726 ms
mainlevel_bg.gif
728 ms
printButton.png
725 ms
emailButton.png
840 ms
15360a7483ae1a1e69e8ff9e86dd4cca.jpg
842 ms
6f3962c82479a4bd35a7b25105025f63.jpg
960 ms
92a5bc4d794fe588ca08dc03e027c5cf.jpg
965 ms
ad8f2aa246687f14ada09b45746fd572.jpg
965 ms
677f17277075e6a26219c9742b328431.jpg
1082 ms
084d5406e2d8818a1b3437d98ed4660a.jpg
1083 ms
27f92c415d33d88d1dfb7216a4d7d685.JPG
1193 ms
2dcf805611521238658950860da96f70.jpg
1190 ms
4b8cdba9852e420fdafb79c2d2f7d2be.jpg
1200 ms
user_top_bg.jpg
1184 ms
user_top_left.jpg
1297 ms
user_top_right.jpg
1299 ms
content_bottom_bg.jpg
1412 ms
border.gif
1415 ms
content_bottom_right.jpg
1414 ms
content_bottom_left.jpg
1420 ms
componentheading.jpg
1533 ms
bottom_right.png
1535 ms
bottom_left.png
1643 ms
trafic.js
250 ms
__utm.gif
12 ms
bottom.png
1554 ms
trafic.png
455 ms
xd_arbiter.php
26 ms
xd_arbiter.php
33 ms
transparent.gif
1331 ms
resize.png
1334 ms
buttons.png
1450 ms
loading.png
1453 ms
5274a911d28c7ab789db015d9a0b8ae3.jpg
1548 ms
393d2f346bc087ac7398be039adbee51.JPG
1539 ms
like_box.php
114 ms
4438a45ada4d1f1f3e42711a61410c38.jpg
1434 ms
kyEKgjk51ZE.css
14 ms
kTub4bakEmM.css
19 ms
q68gy-v_YMF.js
24 ms
tD-4JBbQHh6.js
42 ms
0wM5s1Khldu.js
41 ms
1bNoFZUdlYZ.js
41 ms
10394011_917851214910229_3070930624340044394_n.jpg
53 ms
283627_461299437232078_1486613317_n.jpg
18 ms
306248_419686221391917_1472736062_n.jpg
17 ms
11161350_963320590369091_9200544855919688091_n.jpg
31 ms
11742755_1020145211364231_1338762943226855393_n.jpg
22 ms
wL6VQj7Ab77.png
10 ms
s7jcwEQH7Sx.png
12 ms
I6-MnjEovm5.js
10 ms
pQrUxxo5oQp.js
5 ms
faa.ro accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
faa.ro 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
Page has valid source maps
faa.ro 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
RO
RO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faa.ro can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Faa.ro 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.
faa.ro
Open Graph description is not detected on the main page of Faa. 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: