Access gisfile.com. GISFile | Створення, обмін та публікація інтерактивних карт

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

index.htm

216 ms

easyui.css

210 ms

bootstrap.min.css

306 ms

bsicons.css

211 ms

jquery-1.8.0.min.js

305 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 90% of them (26 requests) were addressed to the original Gisfile.com, 7% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (692 ms) belongs to the original domain Gisfile.com.

Content Size

43.8 kB

After Optimization

26.5 kB

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

HTML Optimization

-76%

Potential reduce by 17.2 kB

Original 22.8 kB
After minification 18.1 kB
After compression 5.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 4.7 kB, which is 20% 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 17.2 kB or 76% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

Original 21.0 kB
After minification 21.0 kB
After compression 20.9 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. This website has mostly compressed JavaScripts.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

UK
Language Claimed

N/A
Encoding

UTF-8

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