Tools & Wizards About Us
feo.ru screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

feo.ru

Сайт о Феодосии и отдыхе в Крыму ☀ Феодосия - курорт на Черном море: проезд, жилье, отдых 2024 - всё есть на сайте Feo.ru

Page Load Speed

5.2 sec in total

First Response

519 ms

Resources Loaded

4.4 sec

Page Rendered

266 ms

feo.ru screenshot

About Website

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

Феодосия древнейший город Крыма на побережье Черного моря - информация о городе, музеях, достопримечательностях, проезде, пляжах и отдыхе в Феодосии

Visit feo.ru

Key Findings

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

Performance Metrics

feo.ru performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

feo.ru

519 ms

www.feo.ru

674 ms

main.css

134 ms

primorsky-place.css

267 ms

resp.css

350 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 42% of them (36 requests) were addressed to the original Feo.ru, 9% (8 requests) were made to St6-21.vk.com and 9% (8 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

992.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Feo.ru 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. 50% of websites need less resources to load. Images take 481.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 115.8 kB

  • Original 142.8 kB
  • After minification 141.2 kB
  • After compression 27.0 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 115.8 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 16.4 kB

  • Original 481.1 kB
  • After minification 464.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. Feo images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 27.0 kB

  • Original 413.7 kB
  • After minification 413.7 kB
  • After compression 386.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

-34%

Potential reduce by 58.0 kB

  • Original 171.8 kB
  • After minification 164.3 kB
  • After compression 113.8 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. Feo.ru needs all CSS files to be minified and compressed as it can save up to 58.0 kB or 34% 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 Feo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

feo.ru

feo.ru

519 ms

www.feo.ru

www.feo.ru

674 ms

main.css

main.css

134 ms

primorsky-place.css

primorsky-place.css

267 ms

resp.css

resp.css

350 ms

unite-gallery-feomod.css

unite-gallery-feomod.css

352 ms

main-nic.css

main-nic.css

389 ms

primorsky-place-nic.css

primorsky-place-nic.css

394 ms

resp-nic.css

resp-nic.css

397 ms

js

js

78 ms

es5-shims.min.js

es5-shims.min.js

374 ms

share.js

share.js

625 ms

informer.min.css

informer.min.css

665 ms

806 ms

jquery.min.js

jquery.min.js

25 ms

resp.js

resp.js

411 ms

unitegallery.min.js

unitegallery.min.js

777 ms

ug-theme-tiles.js

ug-theme-tiles.js

612 ms

ug-theme-compact.js

ug-theme-compact.js

614 ms

ug-theme-slider.js

ug-theme-slider.js

615 ms

ug.init-slider-7tiles-noscroll.js

ug.init-slider-7tiles-noscroll.js

619 ms

analytics.js

analytics.js

215 ms

icon-vk.png

icon-vk.png

677 ms

cycounter

cycounter

837 ms

logo-mini2.png

logo-mini2.png

390 ms

icon-ok.png

icon-ok.png

778 ms

icon-youtube.svg

icon-youtube.svg

799 ms

icon-telegram.png

icon-telegram.png

799 ms

feo_logo-transp.svg

feo_logo-transp.svg

220 ms

feodosiya-09.jpg

feodosiya-09.jpg

893 ms

feodosiya-07.jpg

feodosiya-07.jpg

539 ms

vk-feo-ava.png

vk-feo-ava.png

262 ms

icon-panoramy-360.svg

icon-panoramy-360.svg

263 ms

site-map.gif

site-map.gif

267 ms

forum.htm

forum.htm

396 ms

feotop3hhh.jpg

feotop3hhh.jpg

539 ms

bg5-1.jpg

bg5-1.jpg

395 ms

bg5-2.jpg

bg5-2.jpg

494 ms

bg5-1r_m.jpg

bg5-1r_m.jpg

540 ms

button190.jpg

button190.jpg

540 ms

openapi.a2ed73393cad04481c1dfb3f7794921f.js

openapi.a2ed73393cad04481c1dfb3f7794921f.js

243 ms

collect

collect

23 ms

collect

collect

24 ms

ga-audiences

ga-audiences

88 ms

recent.php

recent.php

403 ms

upload.gif

upload.gif

196 ms

widget_subscribe.php

widget_subscribe.php

381 ms

aci.js

aci.js

602 ms

tag.js

tag.js

1001 ms

code.js

code.js

548 ms

top100.js

top100.js

858 ms

gismeteo.svg

gismeteo.svg

138 ms

forecast-2weeks.ru.svg

forecast-2weeks.ru.svg

224 ms

n.moon.c3.png

n.moon.c3.png

259 ms

d.sun.png

d.sun.png

352 ms

n.moon.png

n.moon.png

382 ms

cover-grid.png

cover-grid.png

166 ms

loader_skype_trans.gif

loader_skype_trans.gif

160 ms

icon-zoom32.png

icon-zoom32.png

165 ms

lightbox-icon-close-compact2.png

lightbox-icon-close-compact2.png

162 ms

lightbox-arrow-left.png

lightbox-arrow-left.png

143 ms

lightbox-arrow-right.png

lightbox-arrow-right.png

263 ms

loader-black3.gif

loader-black3.gif

285 ms

play-button-square.png

play-button-square.png

288 ms

loader-black1.gif

loader-black1.gif

292 ms

counter2

counter2

304 ms

loader_nav21007247412_3.js

loader_nav21007247412_3.js

469 ms

lite.ca486089.css

lite.ca486089.css

534 ms

lang3_2.js

lang3_2.js

389 ms

c3d11fba.2ecb05ac.js

c3d11fba.2ecb05ac.js

422 ms

vkui.43318ab6.css

vkui.43318ab6.css

596 ms

xdm.js

xdm.js

419 ms

al_subscribe.js

al_subscribe.js

421 ms

widget_subscribe.182db5bf.css

widget_subscribe.182db5bf.css

422 ms

base.76878bfc.css

base.76878bfc.css

546 ms

openapi.a2ed73393cad04481c1dfb3f7794921f.js

openapi.a2ed73393cad04481c1dfb3f7794921f.js

382 ms

sync-loader.js

sync-loader.js

855 ms

dyn-goal-config.js

dyn-goal-config.js

155 ms

counter

counter

174 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

503 ms

rtrg

rtrg

128 ms

upload.gif

upload.gif

89 ms

advert.gif

advert.gif

888 ms

sync_cookie_image_decide

sync_cookie_image_decide

183 ms

tracker

tracker

129 ms

Accessibility Review

feo.ru accessibility score

71

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

feo.ru best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

feo.ru SEO score

92

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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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

feo.ru

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