Tools & Wizards About Us
runscrum.io screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

runscrum.io

scagile • The scaled agile project management tool

Page Load Speed

3.9 sec in total

First Response

370 ms

Resources Loaded

2.7 sec

Page Rendered

747 ms

runscrum.io screenshot

About Website

Click here to check amazing Runscrum content. Otherwise, check out these important facts you probably never knew about runscrum.io

Where value flows & business aligns – the revolutionary agile project management tool for scaled organizations. 100% SAFe ready. Get started now for free!

Visit runscrum.io

Key Findings

We analyzed Runscrum.io page load time and found that the first response time was 370 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

runscrum.io performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

runscrum.io

370 ms

281 ms

script.js

39 ms

style.min.css

182 ms

theme.min.css

263 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Runscrum.io, 83% (72 requests) were made to Scagile.io and 9% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (865 ms) relates to the external source Scagile.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 282.4 kB (15%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Runscrum.io main page is 1.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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 218.8 kB

  • Original 264.4 kB
  • After minification 255.4 kB
  • After compression 45.6 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 218.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 1.2 MB
  • After minification 1.2 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. Runscrum images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 40.8 kB

  • Original 253.2 kB
  • After minification 253.2 kB
  • After compression 212.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 40.8 kB or 16% of the original size.

CSS Optimization

-16%

Potential reduce by 21.6 kB

  • Original 130.9 kB
  • After minification 130.9 kB
  • After compression 109.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. Runscrum.io needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (78%)

Requests Now

69

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runscrum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

runscrum.io

runscrum.io

370 ms

281 ms

script.js

script.js

39 ms

style.min.css

style.min.css

182 ms

theme.min.css

theme.min.css

263 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

354 ms

post-6.css

post-6.css

273 ms

elementor-icons.min.css

elementor-icons.min.css

275 ms

swiper.min.css

swiper.min.css

278 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

277 ms

post-83722.css

post-83722.css

351 ms

post-83863.css

post-83863.css

364 ms

post-83780.css

post-83780.css

366 ms

core.min.css

core.min.css

367 ms

style.min.css

style.min.css

368 ms

fontawesome.min.css

fontawesome.min.css

439 ms

solid.min.css

solid.min.css

442 ms

brands.min.css

brands.min.css

455 ms

regular.min.css

regular.min.css

456 ms

jquery.min.js

jquery.min.js

550 ms

jquery-migrate.min.js

jquery-migrate.min.js

460 ms

dwm6rgu.css

dwm6rgu.css

332 ms

widget-animated-headline.min.css

widget-animated-headline.min.css

525 ms

fontawesome-all.min.css

fontawesome-all.min.css

527 ms

fontawesome-v4-shims.css

fontawesome-v4-shims.css

545 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

546 ms

custom-pro-widget-flip-box.min.css

custom-pro-widget-flip-box.min.css

547 ms

custom-widget-icon-box.min.css

custom-widget-icon-box.min.css

611 ms

log

log

409 ms

owl.carousel.css

owl.carousel.css

529 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

551 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

552 ms

widget-posts.min.css

widget-posts.min.css

554 ms

animations.min.css

animations.min.css

654 ms

e-gallery.min.css

e-gallery.min.css

656 ms

post-84151.css

post-84151.css

656 ms

27088745.js

27088745.js

425 ms

hello-frontend.min.js

hello-frontend.min.js

668 ms

main.min.js

main.min.js

668 ms

frhvbuzj.js

frhvbuzj.js

22 ms

ue_mega_menu.js

ue_mega_menu.js

669 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

669 ms

ue-remote-controls.js

ue-remote-controls.js

705 ms

lordicon.js

lordicon.js

3 ms

owl.carousel.min.js

owl.carousel.min.js

619 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

575 ms

e-gallery.min.js

e-gallery.min.js

571 ms

imagesloaded.min.js

imagesloaded.min.js

570 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

571 ms

webpack.runtime.min.js

webpack.runtime.min.js

602 ms

frontend-modules.min.js

frontend-modules.min.js

530 ms

hooks.min.js

hooks.min.js

558 ms

i18n.min.js

i18n.min.js

553 ms

frontend.min.js

frontend.min.js

552 ms

waypoints.min.js

waypoints.min.js

552 ms

core.min.js

core.min.js

600 ms

frontend.min.js

frontend.min.js

528 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

658 ms

jquery.sticky.min.js

jquery.sticky.min.js

553 ms

p.css

p.css

37 ms

cropped-scagile-logo.png

cropped-scagile-logo.png

412 ms

dots-rec_indigo-q4t3n9d294n187v9a1prdqh4oynp69p9296cbrvvz2.png

dots-rec_indigo-q4t3n9d294n187v9a1prdqh4oynp69p9296cbrvvz2.png

412 ms

scagile_Agile-Planning-Tool-2.png

scagile_Agile-Planning-Tool-2.png

808 ms

scagile_Agile-Task-Management-Tool-4.png

scagile_Agile-Task-Management-Tool-4.png

719 ms

scagile_Collaboration-Tool-1.png

scagile_Collaboration-Tool-1.png

865 ms

PI-Planning-Goal_scagile-1024x972.png

PI-Planning-Goal_scagile-1024x972.png

594 ms

complete-sprint_scagile-1024x762.png

complete-sprint_scagile-1024x762.png

505 ms

create-story_scagile-1024x559.png

create-story_scagile-1024x559.png

594 ms

Calculate-Scrum-Velocity_scagile-blog-300x200.jpg

Calculate-Scrum-Velocity_scagile-blog-300x200.jpg

581 ms

1WSJF-scagile-blog-EN-300x200.png

1WSJF-scagile-blog-EN-300x200.png

668 ms

1WSJF-Methode_runScrum-Blog-copy-11-300x200.png

1WSJF-Methode_runScrum-Blog-copy-11-300x200.png

647 ms

Artboard-1.png

Artboard-1.png

647 ms

dots-rec_yellow.png

dots-rec_yellow.png

634 ms

PlusJakartaSans-Regular.ttf

PlusJakartaSans-Regular.ttf

620 ms

d

d

19 ms

d

d

36 ms

d

d

33 ms

d

d

36 ms

d

d

34 ms

d

d

35 ms

d

d

34 ms

fa-brands-400.woff

fa-brands-400.woff

710 ms

fa-brands-400.woff

fa-brands-400.woff

648 ms

fa-solid-900.woff

fa-solid-900.woff

800 ms

fa-solid-900.woff

fa-solid-900.woff

814 ms

fa-regular-400.woff

fa-regular-400.woff

732 ms

fa-regular-400.woff

fa-regular-400.woff

745 ms

Accessibility Review

runscrum.io accessibility score

87

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best Practices

runscrum.io best practices score

83

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

Page has valid source maps

SEO Factors

runscrum.io SEO score

79

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 Runscrum.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 Runscrum.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.

Social Sharing Optimization

runscrum.io

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