Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

moe.st

slchy_routingspace

Page Load Speed

1.4 sec in total

First Response

429 ms

Resources Loaded

887 ms

Page Rendered

107 ms

moe.st screenshot

About Website

Click here to check amazing Moe content for Nigeria. Otherwise, check out these important facts you probably never knew about moe.st

(* ̄3 ̄)╭

Visit moe.st

Key Findings

We analyzed Moe.st page load time and found that the first response time was 429 ms and then it took 994 ms 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.

Performance Metrics

moe.st performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value1.4 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.4 s

100/100

10%

Network Requests Diagram

moe.st

429 ms

bootstrap.min.css

230 ms

style.css

166 ms

components.min.css

174 ms

jquery.min.js

31 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 63% of them (10 requests) were addressed to the original Moe.st, 19% (3 requests) were made to Cdnjs.cloudflare.com and 13% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (429 ms) belongs to the original domain Moe.st.

Page Optimization Overview & Recommendations

Page size can be reduced by 212.2 kB (76%)

Content Size

278.1 kB

After Optimization

65.9 kB

In fact, the total size of Moe.st main page is 278.1 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. 25% of websites need less resources to load. CSS take 140.1 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 4.3 kB

  • Original 6.3 kB
  • After minification 5.3 kB
  • After compression 2.0 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 905 B, which is 14% 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 4.3 kB or 69% of the original size.

JavaScript Optimization

-69%

Potential reduce by 90.6 kB

  • Original 131.8 kB
  • After minification 120.7 kB
  • After compression 41.1 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 90.6 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 117.3 kB

  • Original 140.1 kB
  • After minification 134.1 kB
  • After compression 22.7 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. Moe.st needs all CSS files to be minified and compressed as it can save up to 117.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (64%)

Requests Now

14

After Optimization

5

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

Accessibility Review

moe.st accessibility score

95

Accessibility Issues

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

moe.st best practices score

75

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

moe.st SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

High

robots.txt is not valid

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

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moe.st can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Moe.st 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 Moe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: