1.1 sec in total
171 ms
657 ms
246 ms
Click here to check amazing File content. Otherwise, check out these important facts you probably never knew about file.coffee
Get a slice of the best note-taking app, with toppings of advanced features and a crust of seamless user experience.
Visit file.coffeeWe analyzed File.coffee page load time and found that the first response time was 171 ms and then it took 903 ms 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.
file.coffee performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value3.6 s
60/100
25%
Value5.0 s
64/100
10%
Value2,280 ms
5/100
30%
Value0
100/100
15%
Value10.2 s
25/100
10%
171 ms
318 ms
50 ms
59 ms
58 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original File.coffee, 96% (87 requests) were made to Github.githubassets.com and 1% (1 request) were made to Github.com. The less responsive or slowest element that took the longest time to load (318 ms) relates to the external source Github.com.
Page size can be reduced by 483.1 kB (32%)
1.5 MB
1.0 MB
In fact, the total size of File.coffee main page is 1.5 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. 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. Javascripts take 905.4 kB which makes up the majority of the site volume.
Potential reduce by 291.1 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 291.1 kB or 85% of the original size.
Potential reduce by 23.6 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, File needs image optimization as it can save up to 23.6 kB or 44% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 119.4 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 119.4 kB or 13% of the original size.
Potential reduce by 48.9 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. File.coffee needs all CSS files to be minified and compressed as it can save up to 48.9 kB or 26% of the original size.
Number of requests can be reduced by 85 (96%)
89
4
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of File. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 76 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
file.coffee
171 ms
filehost
318 ms
light-3e154969b9f9.css
50 ms
dark-9c5b7a476542.css
59 ms
primer-primitives-4cf0d59ab51a.css
58 ms
primer-fefb1a332c28.css
68 ms
global-937a43d3e0af.css
78 ms
github-d1e3b63864f7.css
62 ms
repository-0f7cf89e325a.css
56 ms
code-5fa7b9088c7e.css
91 ms
wp-runtime-df2d620b3ef0.js
90 ms
vendors-node_modules_dompurify_dist_purify_js-b73fdff77a4e.js
92 ms
vendors-node_modules_oddbird_popover-polyfill_dist_popover_js-56729c905fe2.js
89 ms
vendors-node_modules_github_arianotify-polyfill_ariaNotify-polyfill_js-node_modules_github_mi-247092-b9c7cf3107b7.js
91 ms
ui_packages_failbot_failbot_ts-aabfa4ec15fe.js
89 ms
environment-2f240f7ed1b3.js
93 ms
vendors-node_modules_primer_behaviors_dist_esm_index_mjs-4aa4b0e95669.js
91 ms
vendors-node_modules_github_selector-observer_dist_index_esm_js-f690fd9ae3d5.js
95 ms
vendors-node_modules_github_relative-time-element_dist_index_js-6d3967acd51c.js
94 ms
vendors-node_modules_github_auto-complete-element_dist_index_js-a164c5ea9f62.js
94 ms
vendors-node_modules_github_text-expander-element_dist_index_js-e40ed7658a74.js
92 ms
vendors-node_modules_github_filter-input-element_dist_index_js-node_modules_github_remote-inp-d1a841-8f251a0656e7.js
94 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_catalyst_lib_index_js-f4b251-f7c3b6081b19.js
95 ms
vendors-node_modules_github_mini-throttle_dist_index_js-node_modules_stacktrace-parser_dist_s-6b2a62-6fef0f2ad42a.js
97 ms
vendors-node_modules_github_file-attachment-element_dist_index_js-node_modules_primer_view-co-eb9d54-74622d897749.js
101 ms
github-elements-36d7dcef5a08.js
96 ms
element-registry-6dd75c7a2977.js
96 ms
vendors-node_modules_github_catalyst_lib_index_js-node_modules_primer_live-region-element_dis-428401-bb66ac5d7472.js
97 ms
vendors-node_modules_braintree_browser-detection_dist_browser-detection_js-node_modules_githu-bb80ec-634de60bacfa.js
97 ms
vendors-node_modules_lit-html_lit-html_js-ce7225a304c5.js
97 ms
vendors-node_modules_github_hydro-analytics-client_dist_analytics-client_js-node_modules_gith-f3aee1-e6893db9c19e.js
98 ms
vendors-node_modules_github_mini-throttle_dist_index_js-node_modules_morphdom_dist_morphdom-e-7c534c-f8a5485c982a.js
102 ms
vendors-node_modules_github_turbo_dist_turbo_es2017-esm_js-858e043fcf76.js
98 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-893f9f-6cf3320416b8.js
99 ms
vendors-node_modules_scroll-anchoring_dist_scroll-anchoring_esm_js-node_modules_stacktrace-pa-a71630-67856ad29bae.js
101 ms
vendors-node_modules_color-convert_index_js-0e07cc183eed.js
103 ms
vendors-node_modules_github_quote-selection_dist_index_js-node_modules_github_session-resume_-9a8cd2-373766bf71f1.js
101 ms
ui_packages_updatable-content_updatable-content_ts-3f4401350bd7.js
105 ms
homepage.png
123 ms
68747470733a2f2f7261696c7761792e6170702f627574746f6e2e737667
124 ms
primer-react-css.45e9ed5ae590728e1b4f.module.css
62 ms
notifications-subscriptions-menu.1bcff9205c241e99cff2.module.css
53 ms
repos-overview.47b2222c697daf78496d.module.css
55 ms
app_assets_modules_github_behaviors_task-list_ts-app_assets_modules_github_sso_ts-ui_packages-900dde-ab87c1d6c5c8.js
77 ms
app_assets_modules_github_sticky-scroll-into-view_ts-112600808cf9.js
60 ms
app_assets_modules_github_behaviors_ajax-error_ts-app_assets_modules_github_behaviors_include-d0d0a6-6faacedf87fe.js
59 ms
app_assets_modules_github_behaviors_commenting_edit_ts-app_assets_modules_github_behaviors_ht-83c235-aeae6fcdf371.js
51 ms
behaviors-aeaa9d751b57.js
56 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_catalyst_lib_index_js-06ff531-bf7e5a3732fd.js
48 ms
notifications-global-54f34167118d.js
47 ms
vendors-node_modules_virtualized-list_es_index_js-node_modules_github_template-parts_lib_index_js-96453a51f920.js
50 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-e53a3f-a93feaebb7e6.js
47 ms
app_assets_modules_github_ref-selector_ts-00df584d9e79.js
48 ms
codespaces-3bf9ff7d0f93.js
46 ms
vendors-node_modules_github_filter-input-element_dist_index_js-node_modules_github_remote-inp-cdab1b-03eba6ef6933.js
48 ms
vendors-node_modules_github_mini-throttle_dist_decorators_js-node_modules_delegated-events_di-e161aa-a6774a3bb897.js
52 ms
vendors-node_modules_github_file-attachment-element_dist_index_js-node_modules_github_remote--b0e14d-7fa7d230862c.js
48 ms
repositories-d27a99fb2b65.js
48 ms
vendors-node_modules_github_mini-throttle_dist_index_js-node_modules_github_catalyst_lib_inde-dbbea9-e73b311a14f1.js
45 ms
code-menu-ab2b8d126a2a.js
49 ms
react-lib-7b7b5264f6c1.js
49 ms
vendors-node_modules_github_mini-throttle_dist_index_js-node_modules_primer_react_lib-esm_Fea-39267a-0c57496bb502.js
55 ms
vendors-node_modules_primer_react_lib-esm_Button_Button_js-411d52ffce67.js
49 ms
vendors-node_modules_primer_react_lib-esm_TooltipV2_Tooltip_js-e39b44f27fbb.js
49 ms
vendors-node_modules_primer_react_lib-esm_ActionList_index_js-ac5b807e06f8.js
49 ms
vendors-node_modules_primer_react_lib-esm_AnchoredOverlay_AnchoredOverlay_js-86d89e63ab43.js
49 ms
vendors-node_modules_primer_react_lib-esm_Text_Text_js-node_modules_primer_react_lib-esm_Text-7845da-776657d09f16.js
47 ms
vendors-node_modules_primer_react_lib-esm_FormControl_FormControl_js-ab48770e9d90.js
48 ms
vendors-node_modules_primer_react_lib-esm_ActionMenu_ActionMenu_js-1feceec002ca.js
49 ms
vendors-node_modules_primer_react_lib-esm_FilteredActionList_FilteredActionListEntry_js-6be2cc10aaf5.js
53 ms
ui_packages_react-core_create-browser-history_ts-ui_packages_react-core_AppContextProvider_ts-ffb979-ed6ff1fbeca4.js
52 ms
ui_packages_react-core_register-partial_ts-a9a9cbc67976.js
50 ms
notifications-subscriptions-menu-a97f78184a6e.js
52 ms
vendors-node_modules_primer_react_lib-esm_KeybindingHint_KeybindingHint_js-node_modules_githu-3fe5e5-779b0a7957e4.js
52 ms
vendors-node_modules_primer_react_lib-esm_Dialog_Dialog_js-node_modules_primer_react_lib-esm_-34d71e-001b2da38ed4.js
51 ms
keyboard-shortcuts-dialog-1257988c5a82.js
49 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-94fd67-9a621ecbf672.js
50 ms
sessions-f3ddee0032e4.js
28 ms
vendors-node_modules_react-router-dom_dist_index_js-c5568c29d405.js
27 ms
vendors-node_modules_tanstack_query-core_build_modern_query_js-node_modules_tanstack_react-qu-e4a133-25f9fad0b763.js
27 ms
vendors-node_modules_tanstack_query-core_build_modern_queryObserver_js-node_modules_tanstack_-defd52-7aa5ebad499a.js
28 ms
vendors-node_modules_primer_react_lib-esm_Dialog_js-node_modules_github_hydro-analytics-clien-531545-69a0fdde1ced.js
28 ms
vendors-node_modules_primer_react_lib-esm_UnderlineNav_index_js-038d9d0ff4a4.js
26 ms
vendors-node_modules_primer_react_lib-esm_Avatar_Avatar_js-node_modules_primer_react_lib-esm_-5bfa75-2192276e3f11.js
29 ms
vendors-node_modules_primer_react_lib-esm_AvatarStack_AvatarStack_js-node_modules_primer_reac-a58e17-cecc8fc2fb9b.js
26 ms
ui_packages_paths_index_ts-022809ef52a5.js
27 ms
ui_packages_ref-selector_RefSelector_tsx-69cea3cdae62.js
27 ms
ui_packages_commit-attribution_index_ts-ui_packages_commit-checks-status_index_ts-ui_packages-8621a7-c8b4ba7bc5d1.js
28 ms
ui_packages_copy-to-clipboard_index_ts-ui_packages_react-core_use-feature-flag_ts-ui_packages-9fa6b6-1a77361c2d20.js
26 ms
ui_packages_code-view-shared_hooks_use-file-page-payload_ts-ui_packages_code-view-shared_comp-4f108f-7f51a25f3f02.js
26 ms
repos-overview-817ebef9dc30.js
27 ms
file.coffee accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Form elements do not have associated labels
Links do not have a discernible name
file.coffee 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
Missing source maps for large first-party JavaScript
file.coffee 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise File.coffee 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 File.coffee 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.
file.coffee
Open Graph data is detected on the main page of File. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: