1.6 sec in total
102 ms
333 ms
1.1 sec
Visit ghcr.io now to see the best up-to-date Ghcr content and also check out these interesting facts you probably never knew about ghcr.io
With GitHub Packages you can safely publish and consume packages within your organization or with the entire world.
Visit ghcr.ioWe analyzed Ghcr.io page load time and found that the first response time was 102 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
ghcr.io performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value5.2 s
23/100
25%
Value4.7 s
69/100
10%
Value1,930 ms
8/100
30%
Value0
100/100
15%
Value10.2 s
25/100
10%
102 ms
35 ms
38 ms
39 ms
69 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ghcr.io, 1% (1 request) were made to Github.com. The less responsive or slowest element that took the longest time to load (104 ms) relates to the external source Github.githubassets.com.
Page size can be reduced by 399.8 kB (33%)
1.2 MB
822.2 kB
In fact, the total size of Ghcr.io main page is 1.2 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 552.4 kB which makes up the majority of the site volume.
Potential reduce by 149.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 149.0 kB or 82% of the original size.
Potential reduce by 0 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. Ghcr images are well optimized though.
Potential reduce by 550 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 250.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. Ghcr.io needs all CSS files to be minified and compressed as it can save up to 250.3 kB or 66% of the original size.
Number of requests can be reduced by 64 (70%)
92
28
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ghcr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
packages
102 ms
light-0eace2597ca3.css
35 ms
dark-a167e256da9c.css
38 ms
primer-primitives-2ef2a46b27ee.css
39 ms
primer-711f412bb361.css
69 ms
global-8215aa0ce496.css
53 ms
github-f4d857cbc96a.css
45 ms
site-dfc0853a912d.css
40 ms
feature-packages-a12a443ee887.css
43 ms
wp-runtime-e55cb5750e3d.js
49 ms
vendors-node_modules_dompurify_dist_purify_js-6890e890956f.js
51 ms
vendors-node_modules_stacktrace-parser_dist_stack-trace-parser_esm_js-node_modules_github_bro-a4c183-79f9611c275b.js
50 ms
vendors-node_modules_oddbird_popover-polyfill_dist_popover_js-1cd1925b631e.js
61 ms
ui_packages_failbot_failbot_ts-479802999bcc.js
63 ms
environment-27057bd9ed0b.js
62 ms
vendors-node_modules_github_selector-observer_dist_index_esm_js-9f960d9b217c.js
97 ms
vendors-node_modules_primer_behaviors_dist_esm_focus-zone_js-086f7a27bac0.js
65 ms
vendors-node_modules_github_relative-time-element_dist_index_js-c76945c5961a.js
63 ms
vendors-node_modules_github_combobox-nav_dist_index_js-node_modules_github_markdown-toolbar-e-820fc0-bc8f02b96749.js
63 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_auto-complete-element-81d69b-df0506cead4e.js
65 ms
vendors-node_modules_github_text-expander-element_dist_index_js-8a621df59e80.js
65 ms
vendors-node_modules_github_filter-input-element_dist_index_js-node_modules_github_remote-inp-b7d8f4-654130b7cde5.js
92 ms
vendors-node_modules_github_file-attachment-element_dist_index_js-node_modules_primer_view-co-3959a9-fb6385ae7d9d.js
96 ms
github-elements-5c1092694681.js
91 ms
element-registry-8574530a6cd5.js
95 ms
vendors-node_modules_github_mini-throttle_dist_index_js-node_modules_github_alive-client_dist-bf5aa2-1b562c29ab8e.js
92 ms
vendors-node_modules_lit-html_lit-html_js-5b376145beff.js
95 ms
vendors-node_modules_morphdom_dist_morphdom-esm_js-5bff297a06de.js
98 ms
vendors-node_modules_github_turbo_dist_turbo_es2017-esm_js-c91f4ad18b62.js
97 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_scroll-anchoring_dist_scro-52dc4b-4fecca2d00e4.js
100 ms
vendors-node_modules_color-convert_index_js-72c9fbde5ad4.js
99 ms
vendors-node_modules_primer_behaviors_dist_esm_dimensions_js-node_modules_github_jtml_lib_index_js-95b84ee6bc34.js
96 ms
vendors-node_modules_github_paste-markdown_dist_index_esm_js-node_modules_github_quote-select-cbac5f-c7885f4526c5.js
99 ms
app_assets_modules_github_updatable-content_ts-ee3fc84d7fb0.js
103 ms
app_assets_modules_github_behaviors_task-list_ts-app_assets_modules_github_onfocus_ts-app_ass-421cec-9de4213015af.js
102 ms
app_assets_modules_github_sticky-scroll-into-view_ts-94209c43e6af.js
101 ms
app_assets_modules_github_behaviors_ajax-error_ts-app_assets_modules_github_behaviors_include-467754-f9bd433e9591.js
104 ms
app_assets_modules_github_behaviors_commenting_edit_ts-app_assets_modules_github_behaviors_ht-83c235-9285faa0e011.js
74 ms
app_assets_modules_github_blob-anchor_ts-app_assets_modules_github_filter-sort_ts-app_assets_-c96432-da3733f430b8.js
68 ms
behaviors-b74cf7d465fa.js
74 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_catalyst_lib_index_js-d0256ebff5cd.js
69 ms
notifications-global-352d84c6cc82.js
67 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_catalyst_lib_index_js-b4a243-ee680693e2b9.js
61 ms
marketing-b8809ed07446.js
63 ms
marketing-packages-1b76d50b84af.js
72 ms
react-lib-1fbfc5be2c18.js
58 ms
vendors-node_modules_primer_octicons-react_dist_index_esm_js-node_modules_primer_react_lib-es-2e8e7c-adc8451a70cf.js
57 ms
vendors-node_modules_primer_react_lib-esm_Box_Box_js-8f8c5e2a2cbf.js
70 ms
vendors-node_modules_primer_react_lib-esm_Button_Button_js-67fe00b5266a.js
51 ms
vendors-node_modules_primer_react_lib-esm_ActionList_index_js-2dd4d13d3ae6.js
52 ms
vendors-node_modules_primer_react_lib-esm_Button_IconButton_js-node_modules_primer_react_lib--23bcad-01764c79fa41.js
52 ms
ui_packages_react-core_create-browser-history_ts-ui_packages_react-core_AppContextProvider_ts-809ab9-4a2cf4ad7f60.js
51 ms
keyboard-shortcuts-dialog-a23eda2bcf8d.js
55 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-94fd67-99519581d0f8.js
53 ms
sessions-585a7232e50a.js
28 ms
bg-top-d2dc18395ef1.png
29 ms
gpr-tab-icon-4612edb4742e.svg
47 ms
bg-publish-f276b8c0a1ab.svg
58 ms
npm-f99daf5917e9.svg
32 ms
docker-219b043842cd.svg
39 ms
nuget-f84d38ebbb3c.svg
28 ms
maven-11a1831b84c7.png
29 ms
gems-a4d43b9bf549.svg
31 ms
gradle-9d367c16140e.svg
29 ms
bg-install-7efe29b55ad9.svg
30 ms
package-docker-32a904dbd1cf.png
36 ms
icon-private-7a8c43c7ded4.png
35 ms
package-npm-ea1d39a8f7a8.png
35 ms
icon-public-263a8bde47ec.png
41 ms
package-ruby-73d123a20fdd.png
34 ms
icon-secure-login-da97e45d4b7a.png
34 ms
icon-integration-d8116306cd00.png
35 ms
icon-cdn-ce47a2a31247.png
63 ms
bg-quote-1-b8f7c8beb4a5.svg
33 ms
cesium-9339e8b27f14.png
42 ms
bg-quote-2-fe4e0174198b.svg
37 ms
yarn-0669dcaf29e9.svg
35 ms
bg-quote-3-9bff604d89a3.svg
44 ms
providence-health-ead85fbb5302.svg
37 ms
icon-publish-07eb5e78b695.png
37 ms
icon-trigger-64aad6024dba.png
47 ms
icon-workflow-0acf5abe4de4.png
36 ms
bg-bottom-f739ddfa2f5e.png
44 ms
packages-15c9065381a8.svg
41 ms
actions-love-611af36591ce.svg
42 ms
download-89f0534acc68.svg
50 ms
x-023c3ca5e173.svg
42 ms
facebook-de85282d23e6.svg
43 ms
linkedin-3c0ace8edb5f.svg
42 ms
youtube-25bc21e924c8.svg
41 ms
twitch-e576606a89a7.svg
40 ms
tiktok-5d12d948d920.svg
39 ms
github-mark-9be88460eaa6.svg
40 ms
ghcr.io accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ghcr.io 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
Missing source maps for large first-party JavaScript
ghcr.io 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 Ghcr.io 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 Ghcr.io 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.
ghcr.io
Open Graph data is detected on the main page of Ghcr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: