Tools & Wizards About Us
reliefline.net screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% 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

  • 91

    SEO

    Google-friendlier than
    70% of websites

reliefline.net

Disaster Relief & Recovery Services | Reliefline.net

Page Load Speed

11.1 sec in total

First Response

1.8 sec

Resources Loaded

8.7 sec

Page Rendered

709 ms

reliefline.net screenshot

About Website

Click here to check amazing Reliefline content. Otherwise, check out these important facts you probably never knew about reliefline.net

Reliefline provides disaster relief services and always ready for supplies of emergency equipment in Asian and African countries for disaster recovery.

Visit reliefline.net

Key Findings

We analyzed Reliefline.net page load time and found that the first response time was 1.8 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

reliefline.net performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.694

7/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

reliefline.net

1754 ms

css

47 ms

bootstrap.css

1585 ms

bootstrap-grid.css

1085 ms

bootstrap-reboot.css

558 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 88% of them (59 requests) were addressed to the original Reliefline.net, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Reliefline.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 630.5 kB (18%)

Content Size

3.6 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Reliefline.net main page is 3.6 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. 30% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 50.2 kB

  • Original 61.8 kB
  • After minification 50.0 kB
  • After compression 11.6 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 11.8 kB, which is 19% 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 50.2 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 85.4 kB

  • Original 2.9 MB
  • After minification 2.8 MB

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. Reliefline images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 211.5 kB

  • Original 293.8 kB
  • After minification 233.5 kB
  • After compression 82.3 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 211.5 kB or 72% of the original size.

CSS Optimization

-87%

Potential reduce by 283.5 kB

  • Original 326.4 kB
  • After minification 263.0 kB
  • After compression 43.0 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. Reliefline.net needs all CSS files to be minified and compressed as it can save up to 283.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (27%)

Requests Now

64

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reliefline. 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 from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

reliefline.net

reliefline.net

1754 ms

css

css

47 ms

bootstrap.css

bootstrap.css

1585 ms

bootstrap-grid.css

bootstrap-grid.css

1085 ms

bootstrap-reboot.css

bootstrap-reboot.css

558 ms

font-awesome.css

font-awesome.css

836 ms

style.css

style.css

834 ms

basic.css

basic.css

824 ms

galleriffic-2.css

galleriffic-2.css

834 ms

jquery.min.js

jquery.min.js

1377 ms

bootstrap.js

bootstrap.js

1941 ms

popper.min.js

popper.min.js

1381 ms

jquery.galleriffic.js

jquery.galleriffic.js

1115 ms

jquery.opacityrollover.js

jquery.opacityrollover.js

1353 ms

js

js

71 ms

element.js

element.js

61 ms

owl.carousel.css

owl.carousel.css

1129 ms

owl.carousel.min.js

owl.carousel.min.js

24 ms

logo.png

logo.png

287 ms

new-banner-5.jpg

new-banner-5.jpg

3506 ms

new-banner-6.jpg

new-banner-6.jpg

2117 ms

arrow.png

arrow.png

276 ms

world-humanitration-summit-certificate-small.jpg

world-humanitration-summit-certificate-small.jpg

561 ms

dihad-participation2016.jpg

dihad-participation2016.jpg

290 ms

ministry-ofcommerce-and-industry-certificate.jpg

ministry-ofcommerce-and-industry-certificate.jpg

1097 ms

ne-pic-1.jpg

ne-pic-1.jpg

842 ms

ne-pic-2.jpg

ne-pic-2.jpg

848 ms

gallery-pic-th1.jpg

gallery-pic-th1.jpg

838 ms

gallery-pic-th2.jpg

gallery-pic-th2.jpg

1117 ms

gallery-pic-th3.jpg

gallery-pic-th3.jpg

1118 ms

gallery-pic-th4.jpg

gallery-pic-th4.jpg

1124 ms

gallery-pic-th5.jpg

gallery-pic-th5.jpg

1371 ms

gallery-pic-th6.jpg

gallery-pic-th6.jpg

1394 ms

gallery-pic-th7.jpg

gallery-pic-th7.jpg

1395 ms

gallery-pic-th8.jpg

gallery-pic-th8.jpg

1403 ms

map.jpg

map.jpg

1650 ms

fb.png

fb.png

1671 ms

tw.png

tw.png

1670 ms

lin.png

lin.png

1679 ms

ins.png

ins.png

1924 ms

yt.png

yt.png

1946 ms

enq-tab.png

enq-tab.png

1948 ms

close-icon.png

close-icon.png

1955 ms

top-arrow.png

top-arrow.png

2199 ms

js

js

55 ms

analytics.js

analytics.js

115 ms

font

font

117 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2201 ms

bg.jpg

bg.jpg

5183 ms

get-in-touch.jpg

get-in-touch.jpg

2144 ms

top-arrow.png

top-arrow.png

2978 ms

water01.png

water01.png

2296 ms

shelter01.png

shelter01.png

2334 ms

tent01.png

tent01.png

2364 ms

clothes01.png

clothes01.png

2569 ms

food01.png

food01.png

2611 ms

medical01.png

medical01.png

2640 ms

collect

collect

12 ms

solar01.png

solar01.png

2748 ms

loader.gif

loader.gif

2784 ms

gallery-pic-big1.jpg

gallery-pic-big1.jpg

2815 ms

gallery-pic-big2.jpg

gallery-pic-big2.jpg

2373 ms

gallery-pic-big3.jpg

gallery-pic-big3.jpg

282 ms

gallery-pic-big4.jpg

gallery-pic-big4.jpg

283 ms

gallery-pic-big5.jpg

gallery-pic-big5.jpg

281 ms

gallery-pic-big6.jpg

gallery-pic-big6.jpg

282 ms

gallery-pic-big7.jpg

gallery-pic-big7.jpg

285 ms

Accessibility Review

reliefline.net accessibility score

79

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

reliefline.net best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

reliefline.net SEO score

91

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

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

High

Tap targets are not sized appropriately

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

reliefline.net

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