Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

earthquake-nepal.com

7.8 Earthquake Nepal April 25, 2015, Kathmandu, Gorkha, quake risk (management)

Page Load Speed

2.6 sec in total

First Response

295 ms

Resources Loaded

1.3 sec

Page Rendered

986 ms

earthquake-nepal.com screenshot

About Website

Visit earthquake-nepal.com now to see the best up-to-date Earthquake Nepal content for Nepal and also check out these interesting facts you probably never knew about earthquake-nepal.com

A strong earthquake (7.8) hit Nepal on April 25, 2015. Earthquake-Nepal.com : Information about (recent) earthquakes and the earthquake risk in Nepal, Kathmandu, Pokhara.

Visit earthquake-nepal.com

Key Findings

We analyzed Earthquake-nepal.com page load time and found that the first response time was 295 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

earthquake-nepal.com performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

earthquake-nepal.com

295 ms

earthquake-nepal.com

470 ms

js

110 ms

cookieconsent.min.js

46 ms

eqn-twitter.jpg

94 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 70% of them (7 requests) were addressed to the original Earthquake-nepal.com, 20% (2 requests) were made to Cdnjs.cloudflare.com and 10% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (470 ms) belongs to the original domain Earthquake-nepal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.5 kB (45%)

Content Size

293.2 kB

After Optimization

161.7 kB

In fact, the total size of Earthquake-nepal.com main page is 293.2 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. 15% of websites need less resources to load. HTML takes 148.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 126.2 kB

  • Original 148.9 kB
  • After minification 117.9 kB
  • After compression 22.7 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 31.1 kB, which is 21% 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 126.2 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 5.4 kB

  • Original 144.3 kB
  • After minification 139.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. Earthquake Nepal images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

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

Accessibility Review

earthquake-nepal.com accessibility score

79

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.

Internationalization and localization

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

Impact

Issue

High

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

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

earthquake-nepal.com best practices score

67

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

earthquake-nepal.com SEO score

67

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Earthquake-nepal.com 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 Earthquake-nepal.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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