Access runnode.com. Site Maintenance

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

runnode.com

53 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Runnode.com and no external sources were called. The less responsive or slowest element that took the longest time to load (53 ms) belongs to the original domain Runnode.com.

Content Size

451.2 kB

After Optimization

441.6 kB

In fact, the total size of Runnode.com main page is 451.2 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 296.1 kB which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 434 B

Original 920 B
After minification 836 B
After compression 486 B

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 434 B or 47% of the original size.

Image Optimization

-2%

Potential reduce by 5.1 kB

Original 296.1 kB
After minification 291.0 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. Runnode images are well optimized though.

CSS Optimization

-3%

Potential reduce by 4.1 kB

Original 154.2 kB
After minification 154.2 kB
After compression 150.1 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. Runnode.com has all CSS files already compressed.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Search Engine Optimization Advices

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

High

Page is blocked from indexing

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runnode.com 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 Runnode.com 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 description is not detected on the main page of Runnode. 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: