1.4 sec in total
254 ms
907 ms
233 ms
Welcome to 1c.fr homepage info - get ready to check 1C best content right away, or after learning these important things about 1c.fr
Découvrez « 1C » en programmation : une philosophie de simplification et d’optimisation. Explorez comment cette approche intègre IA.
Visit 1c.frWe analyzed 1c.fr page load time and found that the first response time was 254 ms and then it took 1.1 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.
1c.fr performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value23.7 s
0/100
25%
Value7.1 s
31/100
10%
Value170 ms
92/100
30%
Value0.128
82/100
15%
Value20.2 s
2/100
10%
254 ms
150 ms
40 ms
65 ms
47 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 1c.fr, 96% (70 requests) were made to Nsa.gov and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (254 ms) belongs to the original domain 1c.fr.
Page size can be reduced by 170.2 kB (25%)
693.1 kB
522.9 kB
In fact, the total size of 1c.fr main page is 693.1 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. 30% of websites need less resources to load. Images take 444.6 kB which makes up the majority of the site volume.
Potential reduce by 23.7 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 23.7 kB or 76% of the original size.
Potential reduce by 651 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. 1C images are well optimized though.
Potential reduce by 105.2 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 105.2 kB or 62% of the original size.
Potential reduce by 40.7 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. 1c.fr needs all CSS files to be minified and compressed as it can save up to 40.7 kB or 85% of the original size.
Number of requests can be reduced by 24 (34%)
70
46
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1C. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
1c.fr
254 ms
www.nsa.gov
150 ms
main.css
40 ms
home.css
65 ms
status.css
47 ms
main.js
92 ms
erecruit.js
68 ms
plugin_detection.js
70 ms
jquery.wtooltip.js
62 ms
AJS.js
69 ms
AJS_fx.js
100 ms
gb_scripts.js
99 ms
gb_styles.css
100 ms
40 ms
ga.js
40 ms
status.shtml
67 ms
bg.jpg
44 ms
header.jpg
46 ms
header_print.jpg
45 ms
bg_content.jpg
42 ms
nav_home-off.jpg
51 ms
nav_aboutnsa-off.jpg
72 ms
nav_academia-off.jpg
70 ms
nav_business-off.jpg
69 ms
nav_careers-off.jpg
73 ms
nav_ia-off.jpg
79 ms
nav_research-off.jpg
94 ms
nav_publicinfo-off.jpg
104 ms
nav_civilliberties-off.jpg
97 ms
nav_rightcorner.jpg
98 ms
main_noflash.jpg
122 ms
home_section1.jpg
123 ms
button_learnMission.jpg
122 ms
home_section2.jpg
126 ms
home_section3.jpg
133 ms
fb2.jpg
131 ms
bg_leftNews.jpg
151 ms
bg_leftNewsHeader.jpg
152 ms
rss.jpg
152 ms
press_room_thumb.jpg
156 ms
bg_rightcolhome.jpg
168 ms
bg_searchBox.jpg
162 ms
button_search.jpg
186 ms
bg_rightCapsule.jpg
183 ms
header_opmInformation.png
182 ms
twitter.png
188 ms
button_IContheRecord.png
189 ms
header_insideNSA.jpg
197 ms
bullet_homeRed.gif
213 ms
bg_careersAtNSA.jpg
212 ms
header_careers.jpg
224 ms
__utm.gif
58 ms
button_exploreCareers.jpg
218 ms
header_business.jpg
180 ms
header_commitment.jpg
189 ms
button_kidsPage.jpg
204 ms
button_ctw.jpg
197 ms
bottom.jpg
188 ms
littlestar.jpg
192 ms
print.css
31 ms
mainmenu.shtml
35 ms
mainmenu.shtml
40 ms
mainmenu.shtml
31 ms
mainmenu.shtml
45 ms
mainmenu.shtml
41 ms
mainmenu.shtml
12 ms
mainmenu.shtml
49 ms
w_close.gif
49 ms
header_bg.gif
52 ms
g_close.gif
52 ms
indicator1.gif
51 ms
bg_dropdown.jpg
44 ms
icon_leaf.gif
31 ms
1c.fr accessibility score
1c.fr 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
Issues were logged in the Issues panel in Chrome Devtools
1c.fr 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1c.fr 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 1c.fr main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
1c.fr
Open Graph description is not detected on the main page of 1C. 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: