Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

jfrog.org

Software Supply Chain Platform for DevOps & Security | JFrog

Page Load Speed

4.1 sec in total

First Response

33 ms

Resources Loaded

3.3 sec

Page Rendered

838 ms

jfrog.org screenshot

About Website

Click here to check amazing JFrog content for Israel. Otherwise, check out these important facts you probably never knew about jfrog.org

The JFrog Platform gives you an end-to-end pipeline to control the flow of your binaries from build to production. Power your software updates to the edge

Visit jfrog.org

Key Findings

We analyzed Jfrog.org page load time and found that the first response time was 33 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

jfrog.org performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value23,260 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value29.8 s

0/100

10%

Network Requests Diagram

jfrog.org

33 ms

www.jfrog.com

1071 ms

style.css

18 ms

prettyPhoto.css

21 ms

main.min.css

49 ms

Our browser made a total of 554 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Jfrog.org, 88% (486 requests) were made to Jfrog.com and 3% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Jfrog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (42%)

Content Size

7.8 MB

After Optimization

4.5 MB

In fact, the total size of Jfrog.org main page is 7.8 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. 80% 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. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 128.8 kB

  • Original 146.1 kB
  • After minification 94.7 kB
  • After compression 17.3 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 51.5 kB, which is 35% 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 128.8 kB or 88% of the original size.

Image Optimization

-31%

Potential reduce by 1.8 MB

  • Original 5.8 MB
  • After minification 4.0 MB

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, JFrog needs image optimization as it can save up to 1.8 MB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 929.2 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 419.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 929.2 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 453.0 kB

  • Original 540.6 kB
  • After minification 468.3 kB
  • After compression 87.6 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. Jfrog.org needs all CSS files to be minified and compressed as it can save up to 453.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 121 (23%)

Requests Now

529

After Optimization

408

The browser has sent 529 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JFrog. 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 15 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

jfrog.org accessibility score

83

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

jfrog.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

jfrog.org SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jfrog.org 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 Jfrog.org 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.

Social Sharing Optimization

Open Graph data is detected on the main page of JFrog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: