4.8 sec in total
541 ms
3.8 sec
467 ms
Welcome to fabcity.paris homepage info - get ready to check Fab City best content right away, or after learning these important things about fabcity.paris
Supporting the actors of the productive city! Fab City Grand Paris coordinates collective and experimental projects in order to develop the vision of the Fab City.
Visit fabcity.parisWe analyzed Fabcity.paris page load time and found that the first response time was 541 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fabcity.paris performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value8.1 s
2/100
25%
Value3.9 s
82/100
10%
Value1,770 ms
10/100
30%
Value0.378
28/100
15%
Value12.2 s
15/100
10%
541 ms
412 ms
506 ms
94 ms
651 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 51% of them (37 requests) were addressed to the original Fabcity.paris, 24% (17 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fabcity.paris.
Page size can be reduced by 510.4 kB (26%)
2.0 MB
1.5 MB
In fact, the total size of Fabcity.paris main page is 2.0 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. 65% of websites need less resources to load. Images take 935.0 kB which makes up the majority of the site volume.
Potential reduce by 161.6 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 161.6 kB or 82% of the original size.
Potential reduce by 10.4 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. Fab City images are well optimized though.
Potential reduce by 338.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 338.5 kB or 42% of the original size.
Potential reduce by 0 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. Fabcity.paris has all CSS files already compressed.
Number of requests can be reduced by 39 (76%)
51
12
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fab City. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
fabcity.paris
541 ms
jquery.min.js
412 ms
jquery-migrate.min.js
506 ms
js
94 ms
hooks.min.js
651 ms
i18n.min.js
774 ms
index.js
852 ms
index.js
851 ms
imagesLoaded.min.js
856 ms
isotope.min.js
957 ms
salient-portfolio.js
868 ms
dlm-xhr.min.js
875 ms
jquery.easing.min.js
942 ms
jquery.mousewheel.min.js
937 ms
priority.js
953 ms
transit.min.js
977 ms
waypoints.js
985 ms
hoverintent.min.js
1023 ms
magnific.js
1029 ms
touchswipe.min.js
1039 ms
caroufredsel.min.js
1046 ms
anime.min.js
1085 ms
superfish.js
1064 ms
init.js
1329 ms
select2.min.js
1127 ms
api.js
58 ms
wp-polyfill.min.js
1212 ms
index.js
1138 ms
e-202437.js
35 ms
js_composer_front.min.js
1194 ms
nectar-delay-javascript.js
1195 ms
css
51 ms
css
26 ms
FCPG-logo-nb_1x.png
143 ms
FCPG-logo-Blanc.png
823 ms
workshop-header-web3.png
706 ms
workshop-header-web5.png
688 ms
workshop-header-web2-1.png
517 ms
spinner-125.gif
823 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
23 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
32 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
62 ms
css
28 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
3 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
33 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
11 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
33 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
33 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
56 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf
65 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf
65 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf
64 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf
64 ms
recaptcha__en.js
24 ms
anchor
35 ms
styles__ltr.css
4 ms
recaptcha__en.js
12 ms
K1x6b-2KMXAL0IlzeahUAOCVah6M7Udib3NOSV9xjhQ.js
32 ms
webworker.js
63 ms
logo_48.png
21 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
24 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
25 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
24 ms
835 ms
recaptcha__en.js
12 ms
transparent.png
97 ms
171106103612CP_mono.woff
133 ms
fontawesome-webfont.svg
448 ms
icomoon.woff
104 ms
380 ms
fontawesome-webfont.woff
247 ms
fabcity.paris accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fabcity.paris 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
fabcity.paris 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
Tap targets are not sized appropriately
EN
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fabcity.paris can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Fabcity.paris 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.
fabcity.paris
Open Graph data is detected on the main page of Fab City. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: