Tools & Wizards About Us
fildex.ru screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

fildex.ru

Fildex.ru - костромской городской информационный портал

Page Load Speed

7.7 sec in total

First Response

487 ms

Resources Loaded

7.1 sec

Page Rendered

162 ms

fildex.ru screenshot

About Website

Visit fildex.ru now to see the best up-to-date Fildex content for Russia and also check out these interesting facts you probably never knew about fildex.ru

Информационный портал города Костромы, объединивший в себе самые полезные для жителей города сервисы, с помощью которых каждый костромич сможет эффективно планировать свой день.

Visit fildex.ru

Key Findings

We analyzed Fildex.ru page load time and found that the first response time was 487 ms and then it took 7.3 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

fildex.ru performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

fildex.ru

487 ms

fildex.ru

3540 ms

general.css

120 ms

uploadifive.css

236 ms

jquery-ui-1.8.23.custom.css

349 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 81% of them (72 requests) were addressed to the original Fildex.ru, 6% (5 requests) were made to Rtbw.acint.net and 3% (3 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Fildex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 51.5 kB (13%)

Content Size

396.2 kB

After Optimization

344.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fildex.ru main page is 396.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. 30% of websites need less resources to load. Images take 236.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 28.7 kB

  • Original 37.8 kB
  • After minification 32.9 kB
  • After compression 9.1 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.9 kB, which is 13% 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 28.7 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 16.3 kB

  • Original 236.9 kB
  • After minification 220.7 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. Fildex images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 3.6 kB

  • Original 103.3 kB
  • After minification 103.0 kB
  • After compression 99.7 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.

CSS Optimization

-16%

Potential reduce by 2.9 kB

  • Original 18.2 kB
  • After minification 18.2 kB
  • After compression 15.3 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. Fildex.ru needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (60%)

Requests Now

83

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fildex.ru

fildex.ru

487 ms

fildex.ru

fildex.ru

3540 ms

general.css

general.css

120 ms

uploadifive.css

uploadifive.css

236 ms

jquery-ui-1.8.23.custom.css

jquery-ui-1.8.23.custom.css

349 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

467 ms

layout.js

layout.js

352 ms

share42.js

share42.js

378 ms

2gis.js

2gis.js

379 ms

user.js

user.js

381 ms

comments.js

comments.js

461 ms

catalog.js

catalog.js

477 ms

news.js

news.js

504 ms

skidki.js

skidki.js

504 ms

afisha.js

afisha.js

506 ms

polls.js

polls.js

576 ms

consult.js

consult.js

579 ms

complaint.js

complaint.js

580 ms

alert.js

alert.js

629 ms

jquery-ui-1.8.23.custom.min.js

jquery-ui-1.8.23.custom.min.js

757 ms

89437.js

89437.js

1138 ms

form.js

form.js

663 ms

n.png

n.png

117 ms

mb_add.png

mb_add.png

127 ms

mb_ram.png

mb_ram.png

116 ms

index.php

index.php

349 ms

index.php

index.php

194 ms

catalogIco.png

catalogIco.png

117 ms

afishaIco.png

afishaIco.png

232 ms

workIco.png

workIco.png

234 ms

zh.png

zh.png

233 ms

us225_b.jpg

us225_b.jpg

253 ms

index.php

index.php

373 ms

index.php

index.php

401 ms

index.php

index.php

807 ms

index.php

index.php

488 ms

index.php

index.php

580 ms

index.php

index.php

572 ms

bottomLogo.png

bottomLogo.png

498 ms

RBK_oplata.png

RBK_oplata.png

515 ms

18-plus.png

18-plus.png

716 ms

mMenu1.png

mMenu1.png

621 ms

razd.jpg

razd.jpg

628 ms

mMenu2.png

mMenu2.png

697 ms

mMenu3.png

mMenu3.png

702 ms

mMenu4.png

mMenu4.png

746 ms

mMenu5.png

mMenu5.png

742 ms

mMenu6.png

mMenu6.png

823 ms

mMenu7.png

mMenu7.png

828 ms

mMenu8.png

mMenu8.png

830 ms

mMenu9.png

mMenu9.png

857 ms

mMenu10.png

mMenu10.png

871 ms

mMenu11.png

mMenu11.png

915 ms

topInfoLineBg.jpg

topInfoLineBg.jpg

948 ms

mb_a.png

mb_a.png

930 ms

findBg.jpg

findBg.jpg

923 ms

2gis.gif

2gis.gif

948 ms

workFilter.gif

workFilter.gif

973 ms

jquery.min.js

jquery.min.js

289 ms

watch.js

watch.js

1 ms

getCatComplaint.php

getCatComplaint.php

1192 ms

work_hover.png

work_hover.png

922 ms

avtoFilter.gif

avtoFilter.gif

952 ms

findBg1.jpg

findBg1.jpg

961 ms

lbShadow.jpg

lbShadow.jpg

900 ms

consIco.png

consIco.png

898 ms

q1.jpg

q1.jpg

920 ms

q2.jpg

q2.jpg

951 ms

boardIco.png

boardIco.png

960 ms

_form.js

_form.js

91 ms

kv.jpg

kv.jpg

861 ms

aci.js

aci.js

389 ms

discIco.png

discIco.png

885 ms

rightPhotoBg.jpg

rightPhotoBg.jpg

867 ms

autoIco.png

autoIco.png

813 ms

estIco.png

estIco.png

825 ms

pollIco.png

pollIco.png

822 ms

bottomShadow.png

bottomShadow.png

811 ms

1

1

655 ms

1

1

784 ms

661 ms

watch.js

watch.js

0 ms

ymcode

ymcode

655 ms

1

1

657 ms

1

1

658 ms

watch.js

watch.js

1 ms

1

1

97 ms

1

1

96 ms

3

3

246 ms

Accessibility Review

fildex.ru accessibility score

56

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.

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

fildex.ru best practices score

50

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fildex.ru SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fildex.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Fildex.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

fildex.ru

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