Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

moxon.net

Mark Moxon's Travel Writing

Page Load Speed

986 ms in total

First Response

81 ms

Resources Loaded

771 ms

Page Rendered

134 ms

moxon.net screenshot

About Website

Visit moxon.net now to see the best up-to-date Moxon content and also check out these interesting facts you probably never knew about moxon.net

Includes over 570 pages of travel writing and advice from 25 countries and six continents, plus over 5000 photographs and at least one good joke...

Visit moxon.net

Key Findings

We analyzed Moxon.net page load time and found that the first response time was 81 ms and then it took 905 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

moxon.net performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value4.4 s

84/100

10%

Network Requests Diagram

moxon.net

81 ms

www.moxon.net

611 ms

base.min.css

9 ms

screen.min.css

8 ms

bullet_points_20120721.png

7 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 98.2 kB (41%)

Content Size

241.0 kB

After Optimization

142.7 kB

In fact, the total size of Moxon.net main page is 241.0 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. 20% of websites need less resources to load. Images take 96.2 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 12.1 kB

  • Original 17.5 kB
  • After minification 16.5 kB
  • After compression 5.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. 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 12.1 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 51 B

  • Original 96.2 kB
  • After minification 96.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. Moxon images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 61.0 kB

  • Original 94.8 kB
  • After minification 94.8 kB
  • After compression 33.8 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 61.0 kB or 64% of the original size.

CSS Optimization

-77%

Potential reduce by 25.0 kB

  • Original 32.5 kB
  • After minification 32.5 kB
  • After compression 7.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. Moxon.net needs all CSS files to be minified and compressed as it can save up to 25.0 kB or 77% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moxon. According to our analytics all requests are already optimized.

Accessibility Review

moxon.net accessibility score

78

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

moxon.net 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

SEO Factors

moxon.net SEO score

85

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 Moxon.net 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 Moxon.net 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 Moxon. 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: