1.3 sec in total
134 ms
842 ms
318 ms
Welcome to forge.sh homepage info - get ready to check Forge best content right away, or after learning these important things about forge.sh
Forge: Fast build system for Kubernetes services
Visit forge.shWe analyzed Forge.sh page load time and found that the first response time was 134 ms and then it took 1.2 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.
forge.sh performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value4.4 s
38/100
25%
Value3.5 s
88/100
10%
Value1,390 ms
16/100
30%
Value0.07
96/100
15%
Value10.4 s
24/100
10%
134 ms
270 ms
51 ms
65 ms
40 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Forge.sh, 32% (9 requests) were made to D33wubrfki0l68.cloudfront.net and 18% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (441 ms) relates to the external source Asciinema.org.
Page size can be reduced by 13.3 kB (35%)
38.5 kB
25.2 kB
In fact, the total size of Forge.sh main page is 38.5 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. 15% of websites need less resources to load. Javascripts take 21.0 kB which makes up the majority of the site volume.
Potential reduce by 13.2 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. This page needs HTML code to be minified as it can gain 3.8 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.2 kB or 76% of the original size.
Potential reduce by 50 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.
Number of requests can be reduced by 7 (33%)
21
14
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
forge.sh
134 ms
forge.sh
270 ms
css
51 ms
css
65 ms
home.css
40 ms
135947.js
441 ms
v2.js
71 ms
buttons.js
39 ms
jquery.min.js
48 ms
gtm.js
165 ms
datawire-logo.svg
27 ms
hero-background.svg
98 ms
kubernetes-docker.svg
103 ms
templates-profiles.svg
119 ms
dependencies.svg
115 ms
canary-deploys.svg
105 ms
zero-infrastructure.svg
117 ms
sassy-penguin.svg
191 ms
forge
105 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
36 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf
41 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
49 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
48 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf
49 ms
analytics.js
23 ms
buttons.html
9 ms
collect
16 ms
js
52 ms
forge.sh 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
forge.sh 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
forge.sh SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forge.sh can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Forge.sh 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.
forge.sh
Open Graph description is not detected on the main page of Forge. 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: