2.8 sec in total
129 ms
2.5 sec
256 ms
Click here to check amazing Fassly content for Romania. Otherwise, check out these important facts you probably never knew about fassly.com
This is your site's landing page.
Visit fassly.comWe analyzed Fassly.com page load time and found that the first response time was 129 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fassly.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value5.9 s
14/100
25%
Value5.8 s
50/100
10%
Value780 ms
37/100
30%
Value0.053
98/100
15%
Value6.6 s
57/100
10%
129 ms
1385 ms
451 ms
50 ms
79 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 88% of them (44 requests) were addressed to the original Fassly.com, 8% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Fassly.com.
Page size can be reduced by 813.3 kB (72%)
1.1 MB
312.8 kB
In fact, the total size of Fassly.com 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. 25% of websites need less resources to load. Javascripts take 633.9 kB which makes up the majority of the site volume.
Potential reduce by 24.3 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 24.3 kB or 77% of the original size.
Potential reduce by 24.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. Obviously, Fassly needs image optimization as it can save up to 24.2 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 472.5 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 472.5 kB or 75% of the original size.
Potential reduce by 292.3 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. Fassly.com needs all CSS files to be minified and compressed as it can save up to 292.3 kB or 84% of the original size.
Number of requests can be reduced by 27 (61%)
44
17
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fassly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
edu
129 ms
1385 ms
css.php
451 ms
cerabox.css
50 ms
css
79 ms
css
97 ms
fonts.css
51 ms
style_advanced_photolightbox.css
87 ms
mootools-core-1.4.5-full-compat-yc.js
129 ms
mootools-more-1.4.0.1-full-compat-yc.js
178 ms
chootools.js
119 ms
core.js
151 ms
core.js
152 ms
smoothbox4.js
175 ms
core.js
208 ms
core.js
252 ms
semods.js
223 ms
cerabox.js
266 ms
jquery.min.js
316 ms
modernizr.js
263 ms
jquery.flexslider.min.js
350 ms
jquery.backstretch.min.js
293 ms
mooModernizr-min.js
284 ms
Observer.js
316 ms
Autocompleter.js
386 ms
Autocompleter.Local.js
334 ms
Autocompleter.Request.js
345 ms
SEAOMooVerticalScroll.js
364 ms
tagger.js
420 ms
fixWidthLightBox.js
408 ms
css.php
143 ms
learning-bg.png
164 ms
loading.gif
36 ms
377 ms
logo-a.png
37 ms
illustration.png
37 ms
home_ico_1.png
44 ms
home_ico_2.png
45 ms
home_ico_3.png
136 ms
home_ico_4.png
135 ms
sprite_white.png
120 ms
black_50.png
120 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
101 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
101 ms
social_icons.png
72 ms
black_80.png
73 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
19 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
19 ms
slider_arrows.png
27 ms
gototop.png
33 ms
fassly.com 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
fassly.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
Page has valid source maps
fassly.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fassly.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Fassly.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.
fassly.com
Open Graph description is not detected on the main page of Fassly. 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: