Tools & Wizards About Us
flood.firetree.net screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

flood.firetree.net

Flood Maps

Page Load Speed

9.2 sec in total

First Response

531 ms

Resources Loaded

8.5 sec

Page Rendered

213 ms

flood.firetree.net screenshot

About Website

Visit flood.firetree.net now to see the best up-to-date Flood Firetree content for Moldova and also check out these interesting facts you probably never knew about flood.firetree.net

Dynamic maps of sea level rise. Will global warming affect you?

Visit flood.firetree.net

Key Findings

We analyzed Flood.firetree.net page load time and found that the first response time was 531 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

flood.firetree.net performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

43/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value1,530 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.182

67/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

flood.firetree.net

531 ms

js

46 ms

common.js

180 ms

flood.js

185 ms

screen.css

207 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 37% of them (46 requests) were addressed to the original Flood.firetree.net, 37% (46 requests) were made to Maps.googleapis.com and 6% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (640 ms) belongs to the original domain Flood.firetree.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 391.1 kB (34%)

Content Size

1.2 MB

After Optimization

772.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 54.8 kB

  • Original 64.3 kB
  • After minification 63.8 kB
  • After compression 9.5 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 54.8 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 11.2 kB

  • Original 602.3 kB
  • After minification 591.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. Flood Firetree images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 321.1 kB

  • Original 491.5 kB
  • After minification 485.3 kB
  • After compression 170.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 321.1 kB or 65% of the original size.

CSS Optimization

-68%

Potential reduce by 4.0 kB

  • Original 5.9 kB
  • After minification 5.4 kB
  • After compression 1.9 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. Flood.firetree.net needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (55%)

Requests Now

119

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flood.firetree.net

flood.firetree.net

531 ms

js

js

46 ms

common.js

common.js

180 ms

flood.js

flood.js

185 ms

screen.css

screen.css

207 ms

cookieconsent.min.js

cookieconsent.min.js

6 ms

show_ads.js

show_ads.js

6 ms

common.css

common.css

94 ms

narrow.css

narrow.css

104 ms

wide.css

wide.css

94 ms

x-click-but21.gif

x-click-but21.gif

113 ms

facebook_32.png

facebook_32.png

114 ms

twitter_32.png

twitter_32.png

115 ms

reddit_32.png

reddit_32.png

114 ms

ca-pub-5231958139916434.js

ca-pub-5231958139916434.js

104 ms

zrt_lookup.html

zrt_lookup.html

50 ms

show_ads_impl.js

show_ads_impl.js

53 ms

widget.min.js

widget.min.js

91 ms

ads

ads

157 ms

osd.js

osd.js

5 ms

handheld.css

handheld.css

93 ms

8573514214996375071

8573514214996375071

35 ms

abg.js

abg.js

38 ms

m_js_controller.js

m_js_controller.js

52 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

75 ms

x_button_blue2.png

x_button_blue2.png

36 ms

s

s

26 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

4 ms

activeview

activeview

13 ms

common.js

common.js

20 ms

util.js

util.js

41 ms

stats.js

stats.js

39 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

192 ms

dark-floating.css

dark-floating.css

14 ms

map.js

map.js

16 ms

ui

ui

59 ms

logo.png

logo.png

38 ms

onion.js

onion.js

32 ms

openhand_8_8.cur

openhand_8_8.cur

45 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

141 ms

controls.js

controls.js

26 ms

z_6

z_6

114 ms

z_6

z_6

111 ms

z_6

z_6

104 ms

z_6

z_6

113 ms

z_6

z_6

191 ms

z_6

z_6

192 ms

z_6

z_6

203 ms

z_6

z_6

212 ms

z_6

z_6

215 ms

z_6

z_6

231 ms

z_6

z_6

269 ms

z_6

z_6

276 ms

z_6

z_6

279 ms

z_6

z_6

310 ms

z_6

z_6

311 ms

z_6

z_6

323 ms

z_6

z_6

355 ms

z_6

z_6

367 ms

z_6

z_6

371 ms

z_6

z_6

412 ms

z_6

z_6

412 ms

z_6

z_6

429 ms

z_6

z_6

446 ms

z_6

z_6

458 ms

z_6

z_6

460 ms

z_6

z_6

514 ms

z_6

z_6

515 ms

z_6

z_6

534 ms

z_6

z_6

537 ms

z_6

z_6

549 ms

z_6

z_6

550 ms

z_6

z_6

615 ms

z_6

z_6

616 ms

z_6

z_6

640 ms

z_6

z_6

627 ms

transparent.png

transparent.png

36 ms

css

css

51 ms

google4.png

google4.png

36 ms

mapcnt6.png

mapcnt6.png

30 ms

sv5.png

sv5.png

58 ms

tmapctrl.png

tmapctrl.png

38 ms

tmapctrl4.png

tmapctrl4.png

40 ms

imgs8.png

imgs8.png

40 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

35 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

82 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

83 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

84 ms

vt

vt

35 ms

vt

vt

32 ms

vt

vt

21 ms

vt

vt

29 ms

vt

vt

35 ms

vt

vt

36 ms

vt

vt

28 ms

vt

vt

30 ms

vt

vt

29 ms

vt

vt

33 ms

vt

vt

36 ms

vt

vt

39 ms

vt

vt

36 ms

vt

vt

49 ms

vt

vt

50 ms

vt

vt

52 ms

vt

vt

53 ms

vt

vt

55 ms

vt

vt

55 ms

vt

vt

57 ms

vt

vt

62 ms

vt

vt

62 ms

vt

vt

73 ms

vt

vt

62 ms

vt

vt

63 ms

vt

vt

70 ms

vt

vt

71 ms

vt

vt

64 ms

vt

vt

72 ms

vt

vt

67 ms

vt

vt

72 ms

vt

vt

75 ms

vt

vt

77 ms

vt

vt

77 ms

vt

vt

78 ms

vt

vt

82 ms

vt

vt

80 ms

Accessibility Review

flood.firetree.net accessibility score

66

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

flood.firetree.net best practices score

83

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

Serves images with low resolution

General

Impact

Issue

High

Missing source maps for large first-party JavaScript

SEO Factors

flood.firetree.net SEO score

69

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

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 doesn't use 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 Flood.firetree.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 Flood.firetree.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

flood.firetree.net

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