Tools & Wizards About Us
fires.ru screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    31% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

fires.ru

СКАНЭКС - мониторинг природных пожаров, карта пожаров Kosmosnimki - wildfire satellite operative monitoring, fires map

Page Load Speed

4.2 sec in total

First Response

594 ms

Resources Loaded

3.3 sec

Page Rendered

325 ms

fires.ru screenshot

About Website

Welcome to fires.ru homepage info - get ready to check Fires best content for Russia right away, or after learning these important things about fires.ru

Карта пожаров. Мониторинг природных пожаров со спутников. Прогноз пожароопасности. Дистанционные системы детектирования и наблюдения пожаров. Global fire map based on remote sensing and location based...

Visit fires.ru

Key Findings

We analyzed Fires.ru page load time and found that the first response time was 594 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fires.ru performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value17.5 s

0/100

10%

TBT (Total Blocking Time)

Value8,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

fires.ru

594 ms

fires.ru

531 ms

fires.css

262 ms

style.css

380 ms

geomixer.css

904 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 67% of them (18 requests) were addressed to the original Fires.ru, 19% (5 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Kosmosnimki.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Kosmosnimki.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.7 kB (27%)

Content Size

77.0 kB

After Optimization

56.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fires.ru main page is 77.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. 35% of websites need less resources to load. CSS take 45.0 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 2.2 kB

  • Original 3.6 kB
  • After minification 3.5 kB
  • After compression 1.4 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 2.2 kB or 62% of the original size.

Image Optimization

-16%

Potential reduce by 437 B

  • Original 2.7 kB
  • After minification 2.2 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. Obviously, Fires needs image optimization as it can save up to 437 B or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-30%

Potential reduce by 7.6 kB

  • Original 25.7 kB
  • After minification 25.7 kB
  • After compression 18.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 7.6 kB or 30% of the original size.

CSS Optimization

-23%

Potential reduce by 10.4 kB

  • Original 45.0 kB
  • After minification 45.0 kB
  • After compression 34.6 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. Fires.ru needs all CSS files to be minified and compressed as it can save up to 10.4 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (70%)

Requests Now

20

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fires.ru

fires.ru

594 ms

fires.ru

fires.ru

531 ms

fires.css

fires.css

262 ms

style.css

style.css

380 ms

geomixer.css

geomixer.css

904 ms

geomixer-src.js

geomixer-src.js

1749 ms

style.css

style.css

381 ms

winnie_2.0.css

winnie_2.0.css

392 ms

pikaday.js

pikaday.js

391 ms

pikaday.css

pikaday.css

390 ms

spatial_query.js

spatial_query.js

408 ms

FireVirtualLayer.js

FireVirtualLayer.js

506 ms

FirePlugin.css

FirePlugin.css

507 ms

config.js

config.js

525 ms

winnie_2.0.js

winnie_2.0.js

654 ms

fire.js

fire.js

530 ms

css

css

50 ms

css

css

25 ms

vectur.png

vectur.png

148 ms

group1.png

group1.png

163 ms

group2.png

group2.png

125 ms

tiny_grid.png

tiny_grid.png

164 ms

zYXgKVElMYYaJe8bpLHnCwDKhdHeEw.woff

zYXgKVElMYYaJe8bpLHnCwDKhdHeEw.woff

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

40 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

42 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

78 ms

Accessibility Review

fires.ru accessibility score

87

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

fires.ru 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

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

fires.ru SEO score

98

Search Engine Optimization Advices

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

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fires.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Fires.ru 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

fires.ru

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