7.7 sec in total
1.3 sec
6.1 sec
232 ms
Welcome to flora.am homepage info - get ready to check Flora best content for Armenia right away, or after learning these important things about flora.am
Օգտվելով Մեր կայքից Դուք կարող եք պատվիրել ծաղիկների առաքում գտնվելով աշխարհի ցանկացած կետում Գյումրի Հայաստան
Visit flora.amWe analyzed Flora.am page load time and found that the first response time was 1.3 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
flora.am performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value10.7 s
0/100
25%
Value10.1 s
9/100
10%
Value50 ms
100/100
30%
Value0.287
42/100
15%
Value9.7 s
28/100
10%
1318 ms
341 ms
1043 ms
341 ms
347 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 85% of them (51 requests) were addressed to the original Flora.am, 5% (3 requests) were made to Image.providesupport.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Flora.am.
Page size can be reduced by 953.6 kB (39%)
2.4 MB
1.5 MB
In fact, the total size of Flora.am main page is 2.4 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. 25% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 48.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. 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 48.1 kB or 85% of the original size.
Potential reduce by 127.1 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. Flora images are well optimized though.
Potential reduce by 739.8 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 739.8 kB or 82% of the original size.
Potential reduce by 38.7 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. Flora.am needs all CSS files to be minified and compressed as it can save up to 38.7 kB or 79% of the original size.
Number of requests can be reduced by 23 (39%)
59
36
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
flora.am
1318 ms
main.css
341 ms
jquery-ui.css
1043 ms
main-menu.css
341 ms
responsiveslides.css
347 ms
jquery.fancybox.css
349 ms
select_jq.css
510 ms
jquery.js
2075 ms
jquery-ui.js
3215 ms
jquery.customSelect.js
520 ms
responsiveslides.js
639 ms
jquery.validate.js
1824 ms
jquery.fancybox.pack.js
860 ms
select_jq.js
839 ms
watermark.jquery.js
1040 ms
snow-plugin.js
1027 ms
main.js
1195 ms
all.js
282 ms
hpictam1.png
244 ms
hphones.png
226 ms
march8.jpg
541 ms
1.jpg
1013 ms
2.jpg
537 ms
3.jpg
704 ms
4.jpg
751 ms
5.jpg
816 ms
6.jpg
1037 ms
7.jpg
1052 ms
8.jpg
1209 ms
9.jpg
1253 ms
10.jpg
1403 ms
11.jpg
1508 ms
12.jpg
1375 ms
empty.jpg
1209 ms
246.jpg
1400 ms
247.jpg
1397 ms
249.jpg
1420 ms
303.jpg
1533 ms
306.jpg
1581 ms
311.jpg
1566 ms
314.jpg
1576 ms
332.jpg
1595 ms
379.jpg
1661 ms
382.jpg
1702 ms
523.jpg
1741 ms
636.jpg
1916 ms
733.jpg
1780 ms
734.jpg
1768 ms
736.jpg
1828 ms
safe-standard.js
87 ms
analytics.js
86 ms
customSelect-arrow.gif
1775 ms
ui-bg_highlight-hard_100_fafaf4_1x100.png
1817 ms
ui-bg_highlight-hard_15_459e00_1x100.png
1846 ms
collect
29 ms
offline-830853046.gif
22 ms
1i2lnv23rl59p0df4nkoxid60o
21 ms
125 ms
xd_arbiter.php
236 ms
xd_arbiter.php
440 ms
flora.am accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA IDs are not unique
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
flora.am 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
flora.am SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
HY
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flora.am can be misinterpreted by Google and other search engines. Our service has detected that Armenian is used on the page, and it does not match the claimed English language. Our system also found out that Flora.am 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.
flora.am
Open Graph description is not detected on the main page of Flora. 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: