Tools & Wizards About Us
run.id screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

run.id

RunID - Race Management

Page Load Speed

6.6 sec in total

First Response

833 ms

Resources Loaded

5.5 sec

Page Rendered

306 ms

run.id screenshot

About Website

Welcome to run.id homepage info - get ready to check Run best content for Indonesia right away, or after learning these important things about run.id

RunID Race Management established based on that simple reasons, to make running a healthy lifestyle with fun & happy faces in every race we are organized.

Visit run.id

Key Findings

We analyzed Run.id page load time and found that the first response time was 833 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

run.id performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value20.8 s

0/100

10%

TBT (Total Blocking Time)

Value990 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value1.207

1/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

run.id

833 ms

main

255 ms

519 ms

settings.css

1005 ms

style.css

2070 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 71% of them (36 requests) were addressed to the original Run.id, 12% (6 requests) were made to Youtube.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Run.id.

Page Optimization Overview & Recommendations

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

Content Size

2.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Run.id main page is 2.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. 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. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 28.4 kB

  • Original 34.2 kB
  • After minification 29.7 kB
  • After compression 5.8 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 4.5 kB, which is 13% 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 28.4 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 19.2 kB

  • Original 942.3 kB
  • After minification 923.1 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. Run images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 671.1 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 392.9 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 671.1 kB or 63% of the original size.

CSS Optimization

-75%

Potential reduce by 328.6 kB

  • Original 437.0 kB
  • After minification 358.9 kB
  • After compression 108.5 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. Run.id needs all CSS files to be minified and compressed as it can save up to 328.6 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (35%)

Requests Now

43

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

run.id

run.id

833 ms

main

main

255 ms

519 ms

settings.css

settings.css

1005 ms

style.css

style.css

2070 ms

owl.carousel.css

owl.carousel.css

937 ms

logo.png

logo.png

932 ms

07afb0d8739f6d1323aacd0621e12f2d_home%20runid_23_slide%201.jpg

07afb0d8739f6d1323aacd0621e12f2d_home%20runid_23_slide%201.jpg

1959 ms

a129db7397e60362fab4b5cd39e18e9f_home%20runid_23_slide%202.jpg

a129db7397e60362fab4b5cd39e18e9f_home%20runid_23_slide%202.jpg

1878 ms

IZ2YXRLH3js

IZ2YXRLH3js

107 ms

714a0d3d2820a03a8e9fd32c7e07a0c1_home%20runid_23_slide%203.jpg

714a0d3d2820a03a8e9fd32c7e07a0c1_home%20runid_23_slide%203.jpg

1439 ms

935b064508dbe1dfcfd2265d584d951d_home%20runid_23_slide%204.jpg

935b064508dbe1dfcfd2265d584d951d_home%20runid_23_slide%204.jpg

1745 ms

1d034f54f0f8f49ce2357739b2cfcccb_raymond.jpg

1d034f54f0f8f49ce2357739b2cfcccb_raymond.jpg

1010 ms

dde57cd60196b70ea4f29f38a43cf925_ben.jpg

dde57cd60196b70ea4f29f38a43cf925_ben.jpg

1265 ms

2793b0c4ced3586e467ce9c8626fabbc_shuban.jpg

2793b0c4ced3586e467ce9c8626fabbc_shuban.jpg

1521 ms

bower.js

bower.js

2196 ms

built.js

built.js

1775 ms

smooth-scroll.js

smooth-scroll.js

1934 ms

js

js

55 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1972 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

2002 ms

owl.carousel.js

owl.carousel.js

2280 ms

3333c2c6761c936fc6a97884a4ee5c39_pahala.jpg

3333c2c6761c936fc6a97884a4ee5c39_pahala.jpg

2060 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

26 ms

base.js

base.js

52 ms

ad_status.js

ad_status.js

162 ms

L24uOtqvNfFRO5TOxiIOVgM50wph5QKjT82e9pNVgC0.js

L24uOtqvNfFRO5TOxiIOVgM50wph5QKjT82e9pNVgC0.js

103 ms

embed.js

embed.js

41 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

38 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

44 ms

Create

Create

92 ms

id

id

80 ms

GenerateIT

GenerateIT

13 ms

css

css

29 ms

caret_down.png

caret_down.png

388 ms

landing1.jpg

landing1.jpg

388 ms

landing2.jpg

landing2.jpg

407 ms

landing3.jpg

landing3.jpg

490 ms

BreuerText.woff

BreuerText.woff

585 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

623 ms

BreuerText-Bold.woff

BreuerText-Bold.woff

661 ms

previous-button.png

previous-button.png

267 ms

next-button.png

next-button.png

267 ms

loader.gif

loader.gif

240 ms

timer.png

timer.png

365 ms

slide-bg.png

slide-bg.png

427 ms

bullet.png

bullet.png

509 ms

large_left.png

large_left.png

476 ms

large_right.png

large_right.png

518 ms

log_event

log_event

24 ms

Accessibility Review

run.id accessibility score

75

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

run.id best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

run.id SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

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 Run.id 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 Run.id 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

run.id

Open Graph description is not detected on the main page of Run. 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: