Tools & Wizards About Us
flormarstore.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

flormarstore.com

لوازم آرایشی فلورمار ، فروشگاه ابنترنتی لوازم آرایشی فلورمار

Page Load Speed

6.4 sec in total

First Response

1.6 sec

Resources Loaded

4 sec

Page Rendered

821 ms

flormarstore.com screenshot

About Website

Click here to check amazing Flormarstore content for Iran. Otherwise, check out these important facts you probably never knew about flormarstore.com

لوازم آرایشی فلورمار ، فروشگاه لوازم فلورمار، بهترین مارک لوازم آرایشی ، تنها فروشگاه اینترنتی رسمی شرکت فلورمار در ایران

Visit flormarstore.com

Key Findings

We analyzed Flormarstore.com page load time and found that the first response time was 1.6 sec and then it took 4.8 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

flormarstore.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.147

77/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

flormarstore.com

1561 ms

jquery-2.1.0.min.js

600 ms

jssor.slider.mini.js

599 ms

menuzord.js

536 ms

RTL-calendars.picker.css

545 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 98% of them (92 requests) were addressed to the original Flormarstore.com, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Arananetwork.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Flormarstore.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 517.7 kB (22%)

Content Size

2.3 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flormarstore.com main page is 2.3 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. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 33.9 kB

  • Original 40.2 kB
  • After minification 38.5 kB
  • After compression 6.3 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 33.9 kB or 84% of the original size.

Image Optimization

-17%

Potential reduce by 323.9 kB

  • Original 1.9 MB
  • After minification 1.6 MB

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. Obviously, Flormarstore needs image optimization as it can save up to 323.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-43%

Potential reduce by 146.8 kB

  • Original 341.5 kB
  • After minification 339.9 kB
  • After compression 194.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 146.8 kB or 43% of the original size.

CSS Optimization

-38%

Potential reduce by 13.1 kB

  • Original 34.7 kB
  • After minification 34.7 kB
  • After compression 21.6 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. Flormarstore.com needs all CSS files to be minified and compressed as it can save up to 13.1 kB or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (49%)

Requests Now

87

After Optimization

44

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flormarstore.com

flormarstore.com

1561 ms

jquery-2.1.0.min.js

jquery-2.1.0.min.js

600 ms

jssor.slider.mini.js

jssor.slider.mini.js

599 ms

menuzord.js

menuzord.js

536 ms

RTL-calendars.picker.css

RTL-calendars.picker.css

545 ms

slide.css

slide.css

159 ms

prettyPhoto_RTL.css

prettyPhoto_RTL.css

547 ms

hover_effects.css

hover_effects.css

577 ms

font-awesome.css

font-awesome.css

578 ms

menuzord-animations.css

menuzord-animations.css

579 ms

fonts.css

fonts.css

584 ms

RTL_system.css

RTL_system.css

746 ms

menu1.css

menu1.css

754 ms

Header~RTL-home~fonts.css

Header~RTL-home~fonts.css

747 ms

Header~RTL-home~index.css

Header~RTL-home~index.css

752 ms

Header~RTL-home~menus.css

Header~RTL-home~menus.css

748 ms

Header~RTL-home~z-divices.css

Header~RTL-home~z-divices.css

747 ms

news.js

news.js

746 ms

products.js

products.js

739 ms

contacts.js

contacts.js

745 ms

memberarea.js

memberarea.js

753 ms

multimedia.js

multimedia.js

757 ms

faq.js

faq.js

786 ms

e_vote.js

e_vote.js

757 ms

newsletter.js

newsletter.js

777 ms

shoppingcard.js

shoppingcard.js

778 ms

area.js

area.js

784 ms

banner.js

banner.js

799 ms

slide.js

slide.js

793 ms

links.js

links.js

808 ms

dmenu.js

dmenu.js

868 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

832 ms

jcarousel.responsive.js

jcarousel.responsive.js

829 ms

nicEdit.js

nicEdit.js

843 ms

jquery.boxloader.min.js

jquery.boxloader.min.js

835 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

846 ms

RTL-home.css

RTL-home.css

912 ms

animateFromTo.js

animateFromTo.js

801 ms

jquery-ui-1.10.3.custom.js

jquery-ui-1.10.3.custom.js

563 ms

jquery.plugin.js

jquery.plugin.js

427 ms

jquery.calendars.all.js

jquery.calendars.all.js

427 ms

jquery.calendars.persian.js

jquery.calendars.persian.js

395 ms

jquery.calendars.persian-fa.js

jquery.calendars.persian-fa.js

396 ms

hover_effects.js

hover_effects.js

394 ms

functions.js

functions.js

390 ms

css

css

27 ms

YekanNumbers.woff

YekanNumbers.woff

623 ms

ico_110.png

ico_110.png

584 ms

R-header.png

R-header.png

535 ms

home.png

home.png

566 ms

club.png

club.png

564 ms

cart.png

cart.png

563 ms

M-header.png

M-header.png

583 ms

arana.png

arana.png

519 ms

L-header.png

L-header.png

111 ms

header-logo.png

header-logo.png

95 ms

bg2.png

bg2.png

105 ms

cu270se2link_s1.png

cu270se2link_s1.png

99 ms

cu270se2link_s2.png

cu270se2link_s2.png

95 ms

cu270se2link_s3.png

cu270se2link_s3.png

97 ms

cu270se2link_s4.png

cu270se2link_s4.png

99 ms

cu270se2link_s5.png

cu270se2link_s5.png

99 ms

cu270se2link_s6.png

cu270se2link_s6.png

129 ms

cu270se2news_s9.png

cu270se2news_s9.png

129 ms

cu270se2news_s12.png

cu270se2news_s12.png

117 ms

cu270se2news_s2.png

cu270se2news_s2.png

136 ms

cu270se2news_s4.png

cu270se2news_s4.png

135 ms

cu270se2news_s3.png

cu270se2news_s3.png

137 ms

cu270se2product_s26.png

cu270se2product_s26.png

237 ms

cu270se2product_1_s21.png

cu270se2product_1_s21.png

243 ms

cu270se2product_s24.png

cu270se2product_s24.png

243 ms

cu270se2product_s27.png

cu270se2product_s27.png

224 ms

cu270se2product_1_s14.png

cu270se2product_1_s14.png

190 ms

cu270se2product_s82.png

cu270se2product_s82.png

246 ms

cu270se2product_s84.png

cu270se2product_s84.png

256 ms

cu270se2product_s85.png

cu270se2product_s85.png

298 ms

cu270se2product_1_s107.png

cu270se2product_1_s107.png

299 ms

cu270se2product_s162.png

cu270se2product_s162.png

287 ms

cu270se2product_1_s193.png

cu270se2product_1_s193.png

292 ms

cu270se2product_s200.png

cu270se2product_s200.png

299 ms

cu270se2product_1_s1788.png

cu270se2product_1_s1788.png

345 ms

cu270se2product_1_s1797.png

cu270se2product_1_s1797.png

347 ms

cu270se2product_1_s1814.png

cu270se2product_1_s1814.png

351 ms

cu270se2news_s13.png

cu270se2news_s13.png

336 ms

cu270se2news_s11.png

cu270se2news_s11.png

337 ms

cu270se2news_s10.png

cu270se2news_s10.png

346 ms

cu270se2news_s14.png

cu270se2news_s14.png

371 ms

cu270se2news_s15.png

cu270se2news_s15.png

369 ms

cu270se2news_s16.png

cu270se2news_s16.png

359 ms

Yekan.woff

Yekan.woff

353 ms

BYekan.woff

BYekan.woff

344 ms

BNazanin.woff

BNazanin.woff

344 ms

BNazaninBold.woff

BNazaninBold.woff

343 ms

BNazaninBold.ttf

BNazaninBold.ttf

88 ms

Accessibility Review

flormarstore.com accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements 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

High

Links do not have a discernible name

Best Practices

flormarstore.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

flormarstore.com SEO score

92

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

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

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

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

flormarstore.com

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