6.9 sec in total
902 ms
5 sec
991 ms
Welcome to fanfan.perm.ru homepage info - get ready to check Fanfan Perm best content for Russia right away, or after learning these important things about fanfan.perm.ru
Купить цветы недорого с доставкой в Перми. В интернет-магазине ФанФан можно заказать букет с подарком!
Visit fanfan.perm.ruWe analyzed Fanfan.perm.ru page load time and found that the first response time was 902 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fanfan.perm.ru performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value12.5 s
0/100
25%
Value7.5 s
27/100
10%
Value3,010 ms
2/100
30%
Value0.284
42/100
15%
Value19.7 s
2/100
10%
902 ms
77 ms
64 ms
56 ms
158 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 70% of them (64 requests) were addressed to the original Fanfan.perm.ru, 13% (12 requests) were made to Vk.com and 2% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Fanfan.perm.ru.
Page size can be reduced by 637.5 kB (30%)
2.1 MB
1.5 MB
In fact, the total size of Fanfan.perm.ru main page is 2.1 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 37.7 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 6.8 kB, which is 14% 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 37.7 kB or 76% of the original size.
Potential reduce by 129.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. Fanfan Perm images are well optimized though.
Potential reduce by 346.2 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 346.2 kB or 72% of the original size.
Potential reduce by 123.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. Fanfan.perm.ru needs all CSS files to be minified and compressed as it can save up to 123.9 kB or 82% of the original size.
Number of requests can be reduced by 39 (44%)
88
49
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanfan Perm. 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 15 to 1 for CSS and as a result speed up the page load time.
fanfan.perm.ru
902 ms
jquery.min.js
77 ms
css
64 ms
share.js
56 ms
core.css
158 ms
reset.css
331 ms
jquery.fancybox.css
333 ms
jquery.fancybox-buttons.css
330 ms
jquery.fancybox-thumbs.css
336 ms
common.css
332 ms
font.css
335 ms
colors.css
487 ms
style.css
484 ms
styles.css
487 ms
template_styles.css
647 ms
core.js
657 ms
core_ajax.js
500 ms
jquery.mousewheel-3.0.6.pack.js
637 ms
jquery.fancybox.pack.js
638 ms
jquery.fancybox-buttons.js
672 ms
jquery.fancybox-media.js
673 ms
jquery.fancybox-thumbs.js
768 ms
localstorage.js
769 ms
script.js
776 ms
incart.js
781 ms
jquery.cookie.js
789 ms
fanfanslider.js
791 ms
script.js
903 ms
script.js
908 ms
close_side_bann.js
910 ms
openapi.js
470 ms
ba.js
248 ms
spread.php
1045 ms
ga.js
120 ms
123.jpg
2592 ms
w8.png
361 ms
bx_default_logo.png
375 ms
cart.png
362 ms
mainmenubg.png
170 ms
search.png
176 ms
loop.png
380 ms
0.jpg
917 ms
1.jpg
789 ms
2.jpg
1212 ms
3.jpg
942 ms
4.jpg
1088 ms
5.jpg
1310 ms
c323c5d214bd8b908d92dbf256cd6361.jpg
1309 ms
e2811792a829e6ca4319968bbd0410dd.jpg
1106 ms
38094633084f156c752433dd0a2353f9.jpg
1310 ms
a4f00ba31fc72540fb300283dfc9d735.jpg
1323 ms
64a4e6ce8f20b56f8bccad142137aff0.jpg
1385 ms
6846149939bc90e4644874c04cf56922.jpg
1443 ms
b45abfa2a2e1c190c7e540fdb3df21db.jpg
1459 ms
6e72c183e2d1378fd25c25720a376672.jpg
1453 ms
7725e7cb9282fe1839af973a536ab0c2.jpg
1487 ms
d4a210aef3bf2b842da730a93bb7c84d.jpg
1569 ms
248f892c29ce73aa8495e9eacb83838d.jpg
1620 ms
1395bb76b8fbe1c5c7127bdf8591f8b0.jpg
1627 ms
amex_blue.jpg
1630 ms
DC.jpg
1689 ms
JCB.jpg
1830 ms
mc_blue.jpg
3022 ms
visa_blue.jpg
2742 ms
sale_button.png
2725 ms
marker-cat.png
1842 ms
button-gallery.png
1958 ms
century_gothic.ttf
2333 ms
watch.js
31 ms
upload.gif
149 ms
ajax_counter.php
2484 ms
loader.gif
2035 ms
widget_community.php
333 ms
__utm.gif
60 ms
bx_stat
367 ms
loader_nav19239_3.js
650 ms
lite.css
837 ms
lite.js
650 ms
lang3_0.js
374 ms
widget_community.css
373 ms
xdm.js
519 ms
al_community.js
519 ms
Z71Aq3AQhus.jpg
328 ms
Ltf98Y40wDY.jpg
997 ms
sfqN4Uet6DI.jpg
1103 ms
sdv4x2v4c1I.jpg
317 ms
bJuRplQTbO0.jpg
556 ms
rdyKGOXatUQ.jpg
546 ms
camera_50.png
158 ms
sHMeQ_2buqs.jpg
1634 ms
w_logo.png
148 ms
print.css
146 ms
fanfan.perm.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fanfan.perm.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fanfan.perm.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanfan.perm.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 Fanfan.perm.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
fanfan.perm.ru
Open Graph description is not detected on the main page of Fanfan Perm. 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: