Tools & Wizards About Us
fidme.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

fidme.com

Fidme, l'app qui facilite et récompense vos achats au quotidien !

Page Load Speed

3.2 sec in total

First Response

200 ms

Resources Loaded

2.3 sec

Page Rendered

682 ms

fidme.com screenshot

About Website

Welcome to fidme.com homepage info - get ready to check Fidme best content for Morocco right away, or after learning these important things about fidme.com

Cartes de fidélité, Tickets de caisse, Bons de réduction, Bons plans... Fidme regroupe tous vos indispensables shopping sur votre mobile !

Visit fidme.com

Key Findings

We analyzed Fidme.com page load time and found that the first response time was 200 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fidme.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value1,570 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.421

23/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

fidme.com

200 ms

www.fidme.com

490 ms

en

121 ms

application-7930dd20ca11f60dba5cc08d4df55cd4.css

168 ms

application-0bc352bbe052b5ff345a98aadc4231a4.js

246 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 69% of them (43 requests) were addressed to the original Fidme.com, 8% (5 requests) were made to Google.com and 8% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fidme.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 868.0 kB (24%)

Content Size

3.6 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fidme.com main page is 3.6 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 33.4 kB

  • Original 43.9 kB
  • After minification 37.8 kB
  • After compression 10.5 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.1 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 33.4 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 39.1 kB

  • Original 2.4 MB
  • After minification 2.3 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. Fidme images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 395.5 kB

  • Original 619.7 kB
  • After minification 607.8 kB
  • After compression 224.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 395.5 kB or 64% of the original size.

CSS Optimization

-71%

Potential reduce by 400.0 kB

  • Original 565.0 kB
  • After minification 563.0 kB
  • After compression 165.0 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. Fidme.com needs all CSS files to be minified and compressed as it can save up to 400.0 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (33%)

Requests Now

58

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fidme.com

fidme.com

200 ms

www.fidme.com

www.fidme.com

490 ms

en

en

121 ms

application-7930dd20ca11f60dba5cc08d4df55cd4.css

application-7930dd20ca11f60dba5cc08d4df55cd4.css

168 ms

application-0bc352bbe052b5ff345a98aadc4231a4.js

application-0bc352bbe052b5ff345a98aadc4231a4.js

246 ms

account.js

account.js

178 ms

api.js

api.js

25 ms

bootstrap-1710dac1f10a4657b4f1bdd68eacdd0b.js

bootstrap-1710dac1f10a4657b4f1bdd68eacdd0b.js

175 ms

smooth_scroll-e9790fb91139f0db0ecb970de3466651.js

smooth_scroll-e9790fb91139f0db0ecb970de3466651.js

175 ms

init-56139e8f66c0dadf2fbe186657f93392.js

init-56139e8f66c0dadf2fbe186657f93392.js

174 ms

index-1325c0b88d867ea92085be8bfe274c04.js

index-1325c0b88d867ea92085be8bfe274c04.js

306 ms

css

css

25 ms

fidme-7cffdb6da86ba6ff48218a329a24a4d2.png

fidme-7cffdb6da86ba6ff48218a329a24a4d2.png

83 ms

slide-01-731031ad8d1f8de66cd085bc15af12dd.jpg

slide-01-731031ad8d1f8de66cd085bc15af12dd.jpg

402 ms

slide-02-939163bc207b11682d178c9f2cee7c1e.jpg

slide-02-939163bc207b11682d178c9f2cee7c1e.jpg

420 ms

slide-03-c2310d963ca1243c9cac338e8a621da8.jpg

slide-03-c2310d963ca1243c9cac338e8a621da8.jpg

417 ms

slide-04-ec8a7d6cfa55557d5f90a9a988d3f8d0.jpg

slide-04-ec8a7d6cfa55557d5f90a9a988d3f8d0.jpg

417 ms

slide-05-d2c04debca4303e67b9ec0db0c3dae98.jpg

slide-05-d2c04debca4303e67b9ec0db0c3dae98.jpg

402 ms

fidme-app-a71471cb5e1af2a1d93a69c6c0de0ea7.png

fidme-app-a71471cb5e1af2a1d93a69c6c0de0ea7.png

244 ms

logos01-22c04dec6124cbb078ff3e716c36e010.png

logos01-22c04dec6124cbb078ff3e716c36e010.png

403 ms

mask-be2ae2b1729af84ee86c5fb44d5e745f.png

mask-be2ae2b1729af84ee86c5fb44d5e745f.png

485 ms

fidme-video-9f6492f998e64a1112cac282e3d7fd1b.png

fidme-video-9f6492f998e64a1112cac282e3d7fd1b.png

483 ms

logos02-65ba7e121d3d5459bdb1a237cd9b74ae.png

logos02-65ba7e121d3d5459bdb1a237cd9b74ae.png

576 ms

glyphicons-halflings-b4c22a0ed1f42188864f0046f0862ecb.png

glyphicons-halflings-b4c22a0ed1f42188864f0046f0862ecb.png

502 ms

bkg_download-c551735a425d080b3961c802c44924e1.png

bkg_download-c551735a425d080b3961c802c44924e1.png

664 ms

store-apple-e416976abb2ee7a783d83a2204ccd0ce.png

store-apple-e416976abb2ee7a783d83a2204ccd0ce.png

503 ms

store-google-2aca992bda31a5565336c53223d04bc7.png

store-google-2aca992bda31a5565336c53223d04bc7.png

561 ms

store-samsung-93998af904ffca00c6452b3eedab3807.png

store-samsung-93998af904ffca00c6452b3eedab3807.png

561 ms

store-opera-9c879a32dd710878119ac585819633ca.png

store-opera-9c879a32dd710878119ac585819633ca.png

585 ms

store-blackberry-7945abc2e3588de53d73ca275d4147b0.png

store-blackberry-7945abc2e3588de53d73ca275d4147b0.png

588 ms

store-windows-a4297bd570ef6d8aec333bc6559c93cc.png

store-windows-a4297bd570ef6d8aec333bc6559c93cc.png

639 ms

store-amazon-87b21f423446713c0ba25a83e9f612b4.png

store-amazon-87b21f423446713c0ba25a83e9f612b4.png

640 ms

store-windows-8-c849f1dde54d1ca3c07633ebefd212b6.png

store-windows-8-c849f1dde54d1ca3c07633ebefd212b6.png

654 ms

section-03-bkg-8fa36984da186f1d6f59748b57e145db.png

section-03-bkg-8fa36984da186f1d6f59748b57e145db.png

1085 ms

twitter-cf390b7cf2fcb5d481fda67c5a734582.png

twitter-cf390b7cf2fcb5d481fda67c5a734582.png

670 ms

facebook-9e9ade0408ed671aecceb335e868dabc.png

facebook-9e9ade0408ed671aecceb335e868dabc.png

720 ms

youtube-0034bf8da6bda8531e01ca068899dc00.png

youtube-0034bf8da6bda8531e01ca068899dc00.png

720 ms

google-3bfff059096c67f1cdd0704584be102b.png

google-3bfff059096c67f1cdd0704584be102b.png

733 ms

rss-1a5029a17ebafd3521338549a2bdfef1.png

rss-1a5029a17ebafd3521338549a2bdfef1.png

743 ms

foursquare-b5b6505c6d44338e0645d3639eebf876.png

foursquare-b5b6505c6d44338e0645d3639eebf876.png

753 ms

fidme_logo-837ababa0d2c9856cc4382f0168cfa1e.png

fidme_logo-837ababa0d2c9856cc4382f0168cfa1e.png

799 ms

kit_en-f1335b93e8236173b15788fd455d446e.png

kit_en-f1335b93e8236173b15788fd455d446e.png

878 ms

bkg-trame-df8e71a026a0191194380cdc0a14ef2f.png

bkg-trame-df8e71a026a0191194380cdc0a14ef2f.png

788 ms

recaptcha__en.js

recaptcha__en.js

54 ms

analytics.js

analytics.js

17 ms

stats

stats

809 ms

3E7pNY9U-uM

3E7pNY9U-uM

85 ms

fontawesome-webfont-dd5a1c0d3986933f85487740205face3.woff

fontawesome-webfont-dd5a1c0d3986933f85487740205face3.woff

776 ms

collect

collect

23 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

26 ms

www-embed-player.js

www-embed-player.js

46 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

23 ms

ad_status.js

ad_status.js

70 ms

nr-885.min.js

nr-885.min.js

79 ms

anchor

anchor

25 ms

styles__ltr.css

styles__ltr.css

8 ms

-FHGegChvKELgmHNPF97Aj33qC9PBXl7UyexHItfpAU.js

-FHGegChvKELgmHNPF97Aj33qC9PBXl7UyexHItfpAU.js

14 ms

webworker.js

webworker.js

19 ms

checkbox_sprite.png

checkbox_sprite.png

13 ms

loading_sprite.png

loading_sprite.png

12 ms

897bd48721

897bd48721

55 ms

recaptcha__en.js

recaptcha__en.js

6 ms

Accessibility Review

fidme.com accessibility score

66

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

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

High

ARIA IDs are not unique

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

fidme.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fidme.com SEO score

89

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

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

fidme.com

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