faras.com

faras.com is SSL secured

Free website and domain report on faras.com

Last Updated: 11th August, 2020 Update Now
Overview

Snoop Summary for faras.com

This is a free and comprehensive report about faras.com. Faras.com is hosted in Ashburn, Virginia in United States on a server with an IP address of 35.173.7.3, where USD is the local currency and the local language is English. If faras.com was to be sold it would possibly be worth $620 USD (based on the daily revenue potential of the website over a 24 month period). Faras.com receives an estimated 293 unique visitors every day - a decent amount of traffic! This report was last updated 11th August, 2020.

About faras.com

Site Preview: faras.com faras.com
Title: Faras App
Description:
Keywords and Tags: online shopping
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$620 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 4,764,331
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 293
Monthly Visitors: 8,927
Yearly Visitors: 107,052
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $25 USD
Yearly Revenue: $305 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: faras.com 9
Domain Name: faras 5
Extension (TLD): com 3

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 81
Performance 85
Accessibility 85
Best Practices 85
SEO 64
Progressive Web App 85
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
85

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for faras.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 1.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 20 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 1.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive faras.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://faras.com/
0
32.252999953926
250
0
301
text/html
https://faras.com/
32.566000008956
67.610000027344
1276
1799
200
text/html
Document
https://faras.com/styles.b24560e022fec02eb718.css
83.693000022322
165.32699996606
90850
505540
200
text/css
Stylesheet
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
84.042999893427
111.66199995205
42721
128788
200
text/javascript
Script
https://faras.com/runtime-es2015.c3cb78a21d9327c48774.js
84.458000026643
105.14599992894
1779
2581
200
application/javascript
Script
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
85.204999893904
113.67899994366
12910
37293
200
application/javascript
Script
https://faras.com/scripts.908f2f2c0684faad402d.js
85.803000023589
159.4000000041
110061
399659
200
application/javascript
Script
https://faras.com/main-es2015.75af76968c91aed387f6.js
85.444000083953
184.29900007322
345937
1455830
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Roboto:400,300,500,700
179.57699997351
197.38500006497
1660
9432
200
text/css
Stylesheet
https://fonts.gstatic.com/s/roboto/v20/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
271.41899988055
274.04699986801
11609
11016
200
font/woff2
Font
https://faras.com/api/e-commerce/get_category_list
494.63000008836
518.06599996053
1492
5300
200
application/json
XHR
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
581.5270000603
584.0409998782
11651
11056
200
font/woff2
Font
https://faras.com/fontawesome-webfont.af7ae505a9eed503f8b8.woff2?v=4.7.0
581.96199988015
630.21399988793
77474
77160
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
585.24599997327
587.98999991268
11615
11020
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
605.98100000061
610.18000007607
11773
11180
200
font/woff2
Font
https://faras.com/api/e-commerce/get_category_list
630.90200000443
652.46500005014
1492
5300
200
application/json
XHR
https://uploads.faras.com/uploads/app_store.png
693.5119999107
756.69299997389
17577
16963
200
image/png
Image
https://uploads.faras.com/uploads/google_play.png
693.78199987113
790.13199987821
22710
22096
200
image/png
Image
https://faras.com/assets/images/logo-faras.jpg
694.0450000111
715.57200001553
4928
4616
200
image/jpeg
Image
https://faras.com/assets/images/report.PNG
694.32300003245
712.12899987586
821
512
200
image/png
Image
https://faras.com/assets/images/bag.PNG
694.57200006582
716.82900004089
972
663
200
image/png
Image
https://res.cloudinary.com/tabaarak/image/upload/v1575525086/load.._fqd2dp.jpg
698.74799996614
716.18600003421
9645
9077
200
image/jpeg
Image
https://uploads.faras.com/uploads/category_images/5c8615037c1cff10d403eef2l6ot.jpg?d=200x200
699.39199998043
749.21700009145
18597
18076
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5f1fdec94f2b0f7fc7031dadpcdi.jpg?d=200x200
699.81599994935
747.63199989684
18902
18380
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0e6wfhv.jpg?d=200x200
700.06599999033
750.00900006853
12286
11765
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0e8cmJG.jpg?d=200x200
700.21599996835
744.45099988952
7169
6649
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0eeLgMh.jpg?d=200x200
700.60899993405
745.20700005814
14650
14128
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5c9761190ab986409cffb796Q2iR.jpg?d=200x200
700.89600002393
761.62800006568
7281
6761
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5cd7e658b817e24f2e327566uVep.jpg?d=200x200
701.2640000321
768.32899986766
10749
10227
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5cfb650f13b656391c638666Dz0h.jpg?d=200x200
701.4719999861
759.86799993552
3022
2502
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5e089e59cd91e072261cca0dWsBZ.jpg?d=200x200
701.85399986804
799.68199995346
25695
25174
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5eaff5fa03d4bf1e7c79304fYSGU.jpg?d=200x200
702.10499991663
736.31599987857
11949
11431
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5ec5399bfcafd57938fff877bTzo.jpg?d=200x200
702.50499993563
775.89699998498
5861
5340
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5ed0c556318d0813f17aaf13dGeK.jpg?d=200x200
702.69700000063
792.30499989353
10681
10160
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5f19f3367dd8912a766d5532sb6b.jpg?d=200x200
702.98799988814
765.78300003894
6224
5704
200
image/webp
Image
https://faras.com/assets/images/user.PNG
703.49300000817
723.04200008512
1209
900
200
image/png
Image
https://faras.com/api/e-commerce/get_products_in_category
738.54500008747
761.16700004786
300
34
200
application/json
XHR
https://faras.com/api/e-commerce/get_category_slides
2173.1410000939
2196.4439998847
1097
829
200
application/json
XHR
https://uploads.faras.com/uploads/ads_mobile_images/5d8331e05f9f2d1ba37a9a4037K9.jpg
2228.8820000831
2303.4910000861
67833
67208
200
image/faras
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
97.431
11.452
148.58
31.559
180.468
21.088
204.576
25.518
234.109
45.931
282.548
19.198
302.093
72.271
379.536
22.924
402.482
123.368
546.148
187.208
733.39
8.003
747.202
14.511
762.43
8.653
772.764
18.62
794.385
8.545
803.93
7.232
824.754
22.376
865.956
5.733
1269.835
6.864
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 36 KiB
Images can slow down the page's load time. Faras.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://uploads.faras.com/uploads/ads_mobile_images/5d8331e05f9f2d1ba37a9a4037K9.jpg
67208
34264
https://uploads.faras.com/uploads/category_images/5e089e59cd91e072261cca0dWsBZ.jpg?d=200x200
25174
2454
Defer offscreen images — Potential savings of 47 KiB
Time to Interactive can be slowed down by resources on the page. Faras.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://uploads.faras.com/uploads/google_play.png
22096
22096
https://uploads.faras.com/uploads/app_store.png
16963
16963
https://res.cloudinary.com/tabaarak/image/upload/v1575525086/load.._fqd2dp.jpg
9077
9077
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Faras.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Faras.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 26 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://uploads.faras.com/uploads/google_play.png
22096
15836
https://uploads.faras.com/uploads/app_store.png
16963
10355
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 40 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Faras.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://faras.com/
0
https://faras.com/
190
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 991 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://faras.com/main-es2015.75af76968c91aed387f6.js
345937
https://faras.com/scripts.908f2f2c0684faad402d.js
110061
https://faras.com/styles.b24560e022fec02eb718.css
90850
https://faras.com/fontawesome-webfont.af7ae505a9eed503f8b8.woff2?v=4.7.0
77474
https://uploads.faras.com/uploads/ads_mobile_images/5d8331e05f9f2d1ba37a9a4037K9.jpg
67833
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
42721
https://uploads.faras.com/uploads/category_images/5e089e59cd91e072261cca0dWsBZ.jpg?d=200x200
25695
https://uploads.faras.com/uploads/google_play.png
22710
https://uploads.faras.com/uploads/category_images/5f1fdec94f2b0f7fc7031dadpcdi.jpg?d=200x200
18902
https://uploads.faras.com/uploads/category_images/5c8615037c1cff10d403eef2l6ot.jpg?d=200x200
18597
Avoids an excessive DOM size — 263 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
263
Maximum DOM Depth
17
Maximum Child Elements
13
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Faras.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 28 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
Zone
Measure
123.85
0.614
Zone:ZoneAwarePromise
Measure
124.605
0.599
Zone:toString
Measure
125.28
0.164
Zone:util
Measure
125.634
0.226
Zone:legacy
Measure
125.89
0.049
Zone:timers
Measure
125.95
0.495
Zone:requestAnimationFrame
Measure
126.465
0.079
Zone:blocking
Measure
126.554
0.111
Zone:EventTarget
Measure
126.685
1.604
Zone:on_property
Measure
128.324
22.84
Zone:customElements
Measure
151.27
0.245
Zone:XHR
Measure
151.54
0.49
Zone:geolocation
Measure
152.065
0.98
Zone:PromiseRejectionEvent
Measure
153.075
0.259
Zone
Mark
123.884
Zone:ZoneAwarePromise
Mark
124.612
Zone:toString
Mark
125.283
Zone:util
Mark
125.643
Zone:legacy
Mark
125.893
Zone:timers
Mark
125.961
Zone:requestAnimationFrame
Mark
126.47
Zone:blocking
Mark
126.558
Zone:EventTarget
Mark
126.682
Zone:on_property
Mark
128.335
Zone:customElements
Mark
151.282
Zone:XHR
Mark
151.542
Zone:geolocation
Mark
152.07
Zone:PromiseRejectionEvent
Mark
153.078
JavaScript execution time — 0.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
376.494
273.73
2.376
https://faras.com/
255.912
3.108
1.269
Unattributable
123.01
33.346
0.343
https://faras.com/main-es2015.75af76968c91aed387f6.js
72.271
0
61.955
Minimizes main-thread work — 0.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
360.414
Style & Layout
175.097
Other
166.283
Rendering
103.483
Script Parsing & Compilation
79.076
Parse HTML & CSS
28.179
Garbage Collection
14.451
Keep request counts low and transfer sizes small — 39 requests • 991 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
39
1014708
Script
5
513408
Image
21
278761
Font
5
124122
Stylesheet
2
92510
Other
5
4631
Document
1
1276
Media
0
0
Third-party
7
100674
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
48308
0
42721
0
9645
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.13037037037037
0.0085014759251275
0.0020606626220172
0.0020606626220172
0.0016065144364367
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
1976
94
https://faras.com/main-es2015.75af76968c91aed387f6.js
222
72
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
851
62

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.15
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 1.2 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 230 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Faras.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://faras.com/styles.b24560e022fec02eb718.css
90850
350
Remove unused CSS — Potential savings of 87 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Faras.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://faras.com/styles.b24560e022fec02eb718.css
90850
89183
Remove unused JavaScript — Potential savings of 296 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://faras.com/main-es2015.75af76968c91aed387f6.js
345937
191526
https://faras.com/scripts.908f2f2c0684faad402d.js
110061
88047
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
42721
23963

Diagnostics

Serve static assets with an efficient cache policy — 18 resources found
Faras.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://uploads.faras.com/uploads/google_play.png
0
22710
https://uploads.faras.com/uploads/app_store.png
0
17577
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
1800000
42721
https://uploads.faras.com/uploads/ads_mobile_images/5d8331e05f9f2d1ba37a9a4037K9.jpg
1184400000
67833
https://uploads.faras.com/uploads/category_images/5e089e59cd91e072261cca0dWsBZ.jpg?d=200x200
1184400000
25695
https://uploads.faras.com/uploads/category_images/5f1fdec94f2b0f7fc7031dadpcdi.jpg?d=200x200
1184400000
18902
https://uploads.faras.com/uploads/category_images/5c8615037c1cff10d403eef2l6ot.jpg?d=200x200
1184400000
18597
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0eeLgMh.jpg?d=200x200
1184400000
14650
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0e6wfhv.jpg?d=200x200
1184400000
12286
https://uploads.faras.com/uploads/category_images/5eaff5fa03d4bf1e7c79304fYSGU.jpg?d=200x200
1184400000
11949
https://uploads.faras.com/uploads/category_images/5cd7e658b817e24f2e327566uVep.jpg?d=200x200
1184400000
10749
https://uploads.faras.com/uploads/category_images/5ed0c556318d0813f17aaf13dGeK.jpg?d=200x200
1184400000
10681
https://uploads.faras.com/uploads/category_images/5c9761190ab986409cffb796Q2iR.jpg?d=200x200
1184400000
7281
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0e8cmJG.jpg?d=200x200
1184400000
7169
https://uploads.faras.com/uploads/category_images/5f19f3367dd8912a766d5532sb6b.jpg?d=200x200
1184400000
6224
https://uploads.faras.com/uploads/category_images/5ec5399bfcafd57938fff877bTzo.jpg?d=200x200
1184400000
5861
https://uploads.faras.com/uploads/category_images/5cfb650f13b656391c638666Dz0h.jpg?d=200x200
1184400000
3022
https://res.cloudinary.com/tabaarak/image/upload/v1575525086/load.._fqd2dp.jpg
2592000000
9645

Opportunities

Preload key requests — Potential savings of 910 ms
Key requests can be preloaded by using '<link rel=preload>'. Faras.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://faras.com/fontawesome-webfont.af7ae505a9eed503f8b8.woff2?v=4.7.0
910

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v20/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
2.6279999874532
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
2.5139998178929
https://faras.com/fontawesome-webfont.af7ae505a9eed503f8b8.woff2?v=4.7.0
48.252000007778
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
2.7439999394119
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
4.1990000754595
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
line: 0
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of faras.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Faras.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Faras.com may provide relevant information that dialogue cannot, by using audio descriptions.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that faras.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.4.1
Google Maps
3.41.8
jQuery
3.4.1
jQuery UI
1.8.3
Angular
8.2.14
Hammer.js
2.0.7
core-js
2.6.10: pure
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://faras.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
2
Medium
3
High
64

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for faras.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of faras.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is not valid — 36 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE html>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
<head>
Syntax not understood
4
<noscript><img
Syntax not understood
5
height="1"
Syntax not understood
6
width="1"
Syntax not understood
7
style="display: none"
Unknown directive
8
src="https://www.facebook.com/tr?id=385528115479260&ev=PageView&noscript=1"
Unknown directive
9
/></noscript>
Syntax not understood
10
<meta charset="utf-8"/>
Syntax not understood
11
<title>
Syntax not understood
12
Online Shopping Site in Africa | Shop for Mobiles, Electronics, Fashion,
Syntax not understood
13
Grocery, & more @Faras.com
Syntax not understood
14
</title>
Syntax not understood
15
<meta charset="utf-8"/>
Syntax not understood
16
<title>Faras App </title>
Syntax not understood
17
<base href="/"/>
Syntax not understood
18
<meta name="viewport" content="width=device-width, initial-scale=1"/>
Syntax not understood
19
<link rel="icon" type="image/x-icon" href="./favicon.ico"/>
Syntax not understood
20
<link rel="manifest" href="manifest.webmanifest">
Syntax not understood
21
<meta name="theme-color" content="#1976d2">
Syntax not understood
22
<link rel="stylesheet" href="styles.b24560e022fec02eb718.css"></head>
Syntax not understood
23
<body style="background-color: #f4f4f4 !important;">
Unknown directive
24
<!-- Google Tag Manager (noscript) -->
Syntax not understood
25
<noscript><iframe
Syntax not understood
26
src="https://www.googletagmanager.com/ns.html?id=GTM-MS66C4W"
Unknown directive
27
height="0"
Syntax not understood
28
width="0"
Syntax not understood
29
style="display:none;visibility:hidden"
Unknown directive
30
></iframe
Syntax not understood
31
></noscript>
Syntax not understood
32
<!-- End Google Tag Manager (noscript) -->
Syntax not understood
33
<app-root></app-root>
Syntax not understood
35
<script type="text/javascript" src="https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&amp;libraries=places,drawing" async="" defer=""></script>
Unknown directive
38
<script src="runtime-es2015.c3cb78a21d9327c48774.js" type="module"></script><script src="runtime-es5.c3cb78a21d9327c48774.js" nomodule defer></script><script src="polyfills-es5.06881e9a7b5b4b468ced.js" nomodule defer></script><script src="polyfills-es2015.8b3d3a455286320c567a.js" type="module"></script><script src="scripts.908f2f2c0684faad402d.js" defer></script><script src="main-es2015.75af76968c91aed387f6.js" type="module"></script><script src="main-es5.75af76968c91aed387f6.js" nomodule defer></script></body>
Syntax not understood
39
</html>
Syntax not understood

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
85

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of faras.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
Current page responds with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` responds with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest meets the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of faras.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://faras.com/

PWA Optimized

Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 66
Performance 43
Accessibility 83
Best Practices 77
SEO 62
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://faras.com/
Updated: 11th August, 2020

8.01 seconds
First Contentful Paint (FCP)
0%
16%
84%

0.19 seconds
First Input Delay (FID)
65%
32%
3%

Simulate loading on mobile
43

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for faras.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Faras.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Faras.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 20 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Faras.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://faras.com/
0
https://faras.com/
630
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 895 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://faras.com/main-es2015.75af76968c91aed387f6.js
345935
https://faras.com/scripts.908f2f2c0684faad402d.js
110076
https://faras.com/styles.b24560e022fec02eb718.css
90844
https://faras.com/fontawesome-webfont.af7ae505a9eed503f8b8.woff2?v=4.7.0
77474
https://uploads.faras.com/uploads/ads_mobile_images/5d8331e05f9f2d1ba37a9a4037K9.jpg
67833
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
42721
https://uploads.faras.com/uploads/google_play.png
22710
https://uploads.faras.com/uploads/app_store.png
17577
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
12917
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
11775
Avoids an excessive DOM size — 263 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
263
Maximum DOM Depth
17
Maximum Child Elements
13
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Faras.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 28 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
Zone
Measure
391.175
0.934
Zone:ZoneAwarePromise
Measure
392.31
0.909
Zone:toString
Measure
393.295
0.139
Zone:util
Measure
393.665
0.24
Zone:legacy
Measure
393.944
0.07
Zone:timers
Measure
394.039
1.571
Zone:requestAnimationFrame
Measure
395.654
0.155
Zone:blocking
Measure
395.835
0.205
Zone:EventTarget
Measure
396.075
16.679
Zone:on_property
Measure
412.83
162.39
Zone:customElements
Measure
582.13
12.779
Zone:XHR
Measure
594.955
9.914
Zone:geolocation
Measure
604.955
12.995
Zone:PromiseRejectionEvent
Measure
618.019
5.211
Zone
Mark
391.268
Zone:ZoneAwarePromise
Mark
392.324
Zone:toString
Mark
393.303
Zone:util
Mark
393.672
Zone:legacy
Mark
393.953
Zone:timers
Mark
394.048
Zone:requestAnimationFrame
Mark
395.665
Zone:blocking
Mark
395.843
Zone:EventTarget
Mark
396.08
Zone:on_property
Mark
412.863
Zone:customElements
Mark
592.303
Zone:XHR
Mark
594.976
Zone:geolocation
Mark
604.975
Zone:PromiseRejectionEvent
Mark
618.041
Keep request counts low and transfer sizes small — 39 requests • 895 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
39
916720
Script
5
513428
Image
21
180735
Font
5
124126
Stylesheet
2
92535
Other
5
4620
Document
1
1276
Media
0
0
Third-party
7
100715
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 18 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
Unattributable
990
1124
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
3286
717
https://faras.com/scripts.908f2f2c0684faad402d.js
9210
604
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
4098
483
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
2772
420
https://faras.com/main-es2015.75af76968c91aed387f6.js
2485
287
Unattributable
786
160
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
6030
153
https://faras.com/
2114
115
https://faras.com/
2229
109
Unattributable
630
97
https://faras.com/styles.b24560e022fec02eb718.css
4003
95
Unattributable
3192
94
Unattributable
2402
83
Unattributable
2338
64
Unattributable
727
59
https://faras.com/
4939
58
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
6183
51

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://faras.com/
0
46.150000067428
239
0
301
text/html
https://faras.com/
46.645000111312
68.291000090539
1276
1799
200
text/html
Document
https://faras.com/styles.b24560e022fec02eb718.css
161.26200021245
249.27800009027
90844
505540
200
text/css
Stylesheet
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
161.52000008151
191.92600017413
42721
128788
200
text/javascript
Script
https://faras.com/runtime-es2015.c3cb78a21d9327c48774.js
161.70800011605
184.42900013179
1779
2581
200
application/javascript
Script
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
162.14400017634
199.39600001089
12917
37293
200
application/javascript
Script
https://faras.com/scripts.908f2f2c0684faad402d.js
170.99300003611
229.49400008656
110076
399659
200
application/javascript
Script
https://faras.com/main-es2015.75af76968c91aed387f6.js
162.64300001785
255.68000017665
345935
1455830
200
application/javascript
Script
https://faras.com/api/e-commerce/get_category_list
1122.6830000523
1153.0240001157
1492
5300
200
application/json
XHR
https://fonts.googleapis.com/css?family=Roboto:400,300,500,700
1138.8250000309
1155.8440001681
1691
10111
200
text/css
Stylesheet
https://faras.com/api/e-commerce/get_category_list
1328.0550001655
1350.8490000386
1492
5300
200
application/json
XHR
https://uploads.faras.com/uploads/app_store.png
1391.9180000667
1436.371000018
17577
16963
200
image/png
Image
https://uploads.faras.com/uploads/google_play.png
1392.0470001176
1433.8800001424
22710
22096
200
image/png
Image
https://faras.com/assets/images/logo-faras.jpg
1392.3650002107
1413.153000176
4928
4616
200
image/jpeg
Image
https://faras.com/assets/images/report.PNG
1392.6660001744
1416.535000084
821
512
200
image/png
Image
https://faras.com/assets/images/bag.PNG
1393.4240001254
1414.2740000971
972
663
200
image/png
Image
https://res.cloudinary.com/tabaarak/image/upload/v1575525086/load.._fqd2dp.jpg
1395.8500002045
1414.9920002092
9651
9077
200
image/jpeg
Image
https://uploads.faras.com/uploads/category_images/5c8615037c1cff10d403eef2l6ot.jpg?d=100x100
1396.2950001005
1568.4980000369
6345
5824
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5f1fdec94f2b0f7fc7031dadpcdi.jpg?d=100x100
1396.6430001892
1495.4160000198
6554
6033
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0e6wfhv.jpg?d=100x100
1396.899000043
1474.811000051
4497
3976
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0e8cmJG.jpg?d=100x100
1397.0790000167
1435.9670002013
2950
2430
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0eeLgMh.jpg?d=100x100
1397.2020000219
1464.581000153
5055
4534
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5c9761190ab986409cffb796Q2iR.jpg?d=100x100
1397.5930002052
1472.5010001566
2847
2330
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5cd7e658b817e24f2e327566uVep.jpg?d=100x100
1397.8580001276
1475.9860001504
3874
3353
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5cfb650f13b656391c638666Dz0h.jpg?d=100x100
1398.1840000488
1452.7620000299
1514
994
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5e089e59cd91e072261cca0dWsBZ.jpg?d=100x100
1398.3790001366
1548.0470000766
8152
7632
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5eaff5fa03d4bf1e7c79304fYSGU.jpg?d=100x100
1398.4960000962
1531.355000101
4255
3738
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5ec5399bfcafd57938fff877bTzo.jpg?d=100x100
1398.5900001135
1493.53600014
2362
1842
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5ed0c556318d0813f17aaf13dGeK.jpg?d=100x100
1399.0480001085
1527.3280001711
3801
3281
200
image/webp
Image
https://uploads.faras.com/uploads/category_images/5f19f3367dd8912a766d5532sb6b.jpg?d=100x100
1399.7930001933
1548.9030000754
2828
2307
200
image/webp
Image
https://faras.com/assets/images/user.PNG
1399.9960001092
1422.4470001645
1209
900
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
1423.754000105
1429.2900001165
11651
11056
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
1429.1260000318
1433.3320001606
11611
11016
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
1444.7290000971
1447.7510000579
11615
11020
200
font/woff2
Font
https://faras.com/fontawesome-webfont.af7ae505a9eed503f8b8.woff2?v=4.7.0
1445.8390001673
1482.2830001358
77474
77160
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
1465.7310000621
1468.5790000949
11775
11180
200
font/woff2
Font
https://faras.com/api/e-commerce/get_products_in_category
1483.0100000836
1507.040000055
300
34
200
application/json
XHR
https://faras.com/api/e-commerce/get_category_slides
2875.7530001458
2918.4740001801
1097
829
200
application/json
XHR
https://uploads.faras.com/uploads/ads_mobile_images/5d8331e05f9f2d1ba37a9a4037K9.jpg
2984.1420000885
3054.9850000534
67833
67208
200
image/faras
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
101.667
28.852
134.401
5.279
139.829
24.276
164.135
14.666
178.831
27.293
234.302
105.111
339.448
9.393
348.881
39.975
388.958
5.399
397.643
9.192
406.853
10.907
417.79
280.954
698.78
15.985
715.016
20.834
735.956
151.016
887.212
71.66
961.048
23.599
984.679
179.342
1167.067
23.812
1190.986
241.529
1434.026
76.595
1511
7.327
1528.893
9.503
1548.723
25.718
1587.69
7.029
1596.029
19.805
1622.12
10.426
1633.82
10.198
1649.111
10.257
1661.322
12.39
1687.3
10.451
1698.265
9.381
1711.128
8.228
1727.931
10.617
1747.255
12.176
1761.413
8.874
1777.958
11.284
1794.499
8.917
1811.089
7.129
1827.931
6.186
1844.508
10.233
1861.147
8.556
1879.815
5.266
1894.668
6.315
1911.251
6.603
1945.069
15.529
1961.547
7.698
2027.754
11.993
2044.538
5.798
2348.094
10.782
2448.359
14.609
2527.811
5.161
2547.374
5.976
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

Total Blocking Time — 380 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 6.1 s
The time taken for the page's main thread to be quiet enough to handle input.
Estimated Input Latency — 60 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive faras.com as laggy when the latency is higher than 0.05 seconds.

Opportunities

Properly size images — Potential savings of 67 KiB
Images can slow down the page's load time. Faras.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://uploads.faras.com/uploads/ads_mobile_images/5d8331e05f9f2d1ba37a9a4037K9.jpg
67208
53020
https://uploads.faras.com/uploads/google_play.png
22096
15374
Defer offscreen images — Potential savings of 25 KiB
Time to Interactive can be slowed down by resources on the page. Faras.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://uploads.faras.com/uploads/app_store.png
16963
16963
https://res.cloudinary.com/tabaarak/image/upload/v1575525086/load.._fqd2dp.jpg
9077
9077
Remove unused CSS — Potential savings of 87 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Faras.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://faras.com/styles.b24560e022fec02eb718.css
90844
89153
Serve images in next-gen formats — Potential savings of 26 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://uploads.faras.com/uploads/google_play.png
22096
15836
https://uploads.faras.com/uploads/app_store.png
16963
10355

Diagnostics

Serve static assets with an efficient cache policy — 18 resources found
Faras.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://uploads.faras.com/uploads/google_play.png
0
22710
https://uploads.faras.com/uploads/app_store.png
0
17577
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
1800000
42721
https://uploads.faras.com/uploads/ads_mobile_images/5d8331e05f9f2d1ba37a9a4037K9.jpg
1184400000
67833
https://uploads.faras.com/uploads/category_images/5e089e59cd91e072261cca0dWsBZ.jpg?d=100x100
1184400000
8152
https://uploads.faras.com/uploads/category_images/5f1fdec94f2b0f7fc7031dadpcdi.jpg?d=100x100
1184400000
6554
https://uploads.faras.com/uploads/category_images/5c8615037c1cff10d403eef2l6ot.jpg?d=100x100
1184400000
6345
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0eeLgMh.jpg?d=100x100
1184400000
5055
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0e6wfhv.jpg?d=100x100
1184400000
4497
https://uploads.faras.com/uploads/category_images/5eaff5fa03d4bf1e7c79304fYSGU.jpg?d=100x100
1184400000
4255
https://uploads.faras.com/uploads/category_images/5cd7e658b817e24f2e327566uVep.jpg?d=100x100
1184400000
3874
https://uploads.faras.com/uploads/category_images/5ed0c556318d0813f17aaf13dGeK.jpg?d=100x100
1184400000
3801
https://uploads.faras.com/uploads/category_images/5c88a08a783f8911d607f0e8cmJG.jpg?d=100x100
1184400000
2950
https://uploads.faras.com/uploads/category_images/5c9761190ab986409cffb796Q2iR.jpg?d=100x100
1184400000
2847
https://uploads.faras.com/uploads/category_images/5f19f3367dd8912a766d5532sb6b.jpg?d=100x100
1184400000
2828
https://uploads.faras.com/uploads/category_images/5ec5399bfcafd57938fff877bTzo.jpg?d=100x100
1184400000
2362
https://uploads.faras.com/uploads/category_images/5cfb650f13b656391c638666Dz0h.jpg?d=100x100
1184400000
1514
https://res.cloudinary.com/tabaarak/image/upload/v1575525086/load.._fqd2dp.jpg
2592000000
9651
Reduce JavaScript execution time — 3.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
2203.74
1248.056
17.792
Unattributable
1997.236
911.076
1.36
https://faras.com/
1863.116
35.364
3.7
https://faras.com/scripts.908f2f2c0684faad402d.js
620.224
385.9
74.504
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
420.444
347.088
19.932
https://faras.com/main-es2015.75af76968c91aed387f6.js
286.64
0
246.304
https://faras.com/styles.b24560e022fec02eb718.css
95.248
0
0

Metrics

First Contentful Paint — 5.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 6.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 8.7 s
The timing of the largest text or image that is painted.
Time to Interactive — 8.0 s
The time taken for the page to become fully interactive.

Other

Max Potential First Input Delay — 380 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 5.2 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 10876.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 930 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Faras.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://faras.com/styles.b24560e022fec02eb718.css
90844
1680
Remove unused JavaScript — Potential savings of 296 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://faras.com/main-es2015.75af76968c91aed387f6.js
345935
191575
https://faras.com/scripts.908f2f2c0684faad402d.js
110076
88059
https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&libraries=places,drawing
42721
23963
Preload key requests — Potential savings of 4,980 ms
Key requests can be preloaded by using '<link rel=preload>'. Faras.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://faras.com/fontawesome-webfont.af7ae505a9eed503f8b8.woff2?v=4.7.0
4980

Diagnostics

Minimize main-thread work — 7.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2927.484
Other
1732.792
Style & Layout
1556.544
Rendering
644.712
Script Parsing & Compilation
365.572
Parse HTML & CSS
210.592
Garbage Collection
96.352
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
5.5360000114888
https://fonts.gstatic.com/s/roboto/v20/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
4.2060001287609
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
3.0219999607652
https://faras.com/fontawesome-webfont.af7ae505a9eed503f8b8.woff2?v=4.7.0
36.443999968469
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
2.8480000328273
Reduce the impact of third-party code — Third-party code blocked the main thread for 300 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
42721
298.888
48343
0
9651
0
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://faras.com/polyfills-es2015.8b3d3a455286320c567a.js
line: 0
83

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of faras.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Faras.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Faras.com may provide relevant information that dialogue cannot, by using audio descriptions.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
77

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that faras.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.4.1
Google Maps
3.41.8
jQuery
3.4.1
jQuery UI
1.8.3
Angular
8.2.14
Hammer.js
2.0.7
core-js
2.6.10: pure
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://faras.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
2
Medium
3
High

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://faras.com/assets/images/logo-faras.jpg
100 x 61
100 x 61
263 x 161
https://faras.com/assets/images/user.PNG
28 x 30
28 x 30
74 x 79
https://faras.com/assets/images/bag.PNG
20 x 30
22 x 33
53 x 79
62

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for faras.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of faras.com on mobile screens.
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is not valid — 36 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE html>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
<head>
Syntax not understood
4
<noscript><img
Syntax not understood
5
height="1"
Syntax not understood
6
width="1"
Syntax not understood
7
style="display: none"
Unknown directive
8
src="https://www.facebook.com/tr?id=385528115479260&ev=PageView&noscript=1"
Unknown directive
9
/></noscript>
Syntax not understood
10
<meta charset="utf-8"/>
Syntax not understood
11
<title>
Syntax not understood
12
Online Shopping Site in Africa | Shop for Mobiles, Electronics, Fashion,
Syntax not understood
13
Grocery, & more @Faras.com
Syntax not understood
14
</title>
Syntax not understood
15
<meta charset="utf-8"/>
Syntax not understood
16
<title>Faras App </title>
Syntax not understood
17
<base href="/"/>
Syntax not understood
18
<meta name="viewport" content="width=device-width, initial-scale=1"/>
Syntax not understood
19
<link rel="icon" type="image/x-icon" href="./favicon.ico"/>
Syntax not understood
20
<link rel="manifest" href="manifest.webmanifest">
Syntax not understood
21
<meta name="theme-color" content="#1976d2">
Syntax not understood
22
<link rel="stylesheet" href="styles.b24560e022fec02eb718.css"></head>
Syntax not understood
23
<body style="background-color: #f4f4f4 !important;">
Unknown directive
24
<!-- Google Tag Manager (noscript) -->
Syntax not understood
25
<noscript><iframe
Syntax not understood
26
src="https://www.googletagmanager.com/ns.html?id=GTM-MS66C4W"
Unknown directive
27
height="0"
Syntax not understood
28
width="0"
Syntax not understood
29
style="display:none;visibility:hidden"
Unknown directive
30
></iframe
Syntax not understood
31
></noscript>
Syntax not understood
32
<!-- End Google Tag Manager (noscript) -->
Syntax not understood
33
<app-root></app-root>
Syntax not understood
35
<script type="text/javascript" src="https://maps.googleapis.com/maps/api/js?key=AIzaSyD1g7gGHe0pwN5dheZGMXBxFQRcMG5LzBY&amp;libraries=places,drawing" async="" defer=""></script>
Unknown directive
38
<script src="runtime-es2015.c3cb78a21d9327c48774.js" type="module"></script><script src="runtime-es5.c3cb78a21d9327c48774.js" nomodule defer></script><script src="polyfills-es5.06881e9a7b5b4b468ced.js" nomodule defer></script><script src="polyfills-es2015.8b3d3a455286320c567a.js" type="module"></script><script src="scripts.908f2f2c0684faad402d.js" defer></script><script src="main-es2015.75af76968c91aed387f6.js" type="module"></script><script src="main-es5.75af76968c91aed387f6.js" nomodule defer></script></body>
Syntax not understood
39
</html>
Syntax not understood

Mobile Friendly

Document doesn't use legible font sizes — 39.19% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.info-wrap[_ngcontent-vxi-c0] a.title[_ngcontent-vxi-c0]
50.92%
11.2px
._2nhb[_ngcontent-vxi-c7] ._1F92[_ngcontent-vxi-c7] ._3Qsk[_ngcontent-vxi-c7] ._2egn[_ngcontent-vxi-c7]
9.89%
10px
39.19%
≥ 12px

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
Hosting

Server Location

Server IP Address: 35.173.7.3
Continent: North America
Country: United States
United States Flag
Region: Virginia
City: Ashburn
Longitude: -77.4728
Latitude: 39.0481
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Amazon Technologies Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: faras.com
Issued By: Amazon
Valid From: 11th January, 2020
Valid To: 11th February, 2021
Subject: CN = faras.com
Hash: 868b4130
Issuer: CN = Amazon
OU = Server CA 1B
O = Amazon
S = US
Version: 2
Serial Number: 4393995502292756875009135645680845138
Serial Number (Hex): 034E40B44FC5C56A27FF43C02AE5C152
Valid From: 11th January, 2024
Valid To: 11th February, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:59:A4:66:06:52:A0:7B:95:92:3C:A3:94:07:27:96:74:5B:F9:3D:D0
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.sca1b.amazontrust.com/sca1b.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.2
Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://ocsp.sca1b.amazontrust.com
CA Issuers - URI:http://crt.sca1b.amazontrust.com/sca1b.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : A4:B9:09:90:B4:18:58:14:87:BB:13:A2:CC:67:70:0A:
3C:35:98:04:F9:1B:DF:B8:E3:77:CD:0E:C8:0D:DC:10
Timestamp : Jan 11 08:27:56.853 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:70:EC:58:13:D0:FB:95:8B:44:33:E7:71:
40:96:CA:DA:B4:C4:BC:5A:47:16:16:C1:2E:C3:14:83:
96:61:CB:E9:02:21:00:F5:F3:68:9C:76:8B:9B:92:7D:
C2:EA:5C:C3:23:95:1F:0A:E4:68:B2:60:F1:82:77:DF:
B3:02:D8:AC:E8:D6:AD
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 87:75:BF:E7:59:7C:F8:8C:43:99:5F:BD:F3:6E:FF:56:
8D:47:56:36:FF:4A:B5:60:C1:B4:EA:FF:5E:A0:83:0F
Timestamp : Jan 11 08:27:57.005 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:91:E6:B7:61:C2:95:89:42:17:E1:B9:
9B:C1:A2:B9:A3:24:55:67:86:80:2F:2E:C1:08:41:41:
EF:03:BB:CC:AD:02:20:03:72:3E:2D:84:AE:F3:28:15:
81:75:FB:38:2B:0C:81:DE:03:06:73:5C:78:D3:15:76:
7D:21:BE:45:40:B0:D8
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.faras.com
DNS:faras.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
faras.com. 107.23.192.163 IN 59
faras.com. 35.173.7.3 IN 59

NS Records

Host Nameserver Class TTL
faras.com. ns-1083.awsdns-07.org. IN 21599
faras.com. ns-1808.awsdns-34.co.uk. IN 21599
faras.com. ns-32.awsdns-04.com. IN 21599
faras.com. ns-738.awsdns-28.net. IN 21599

MX Records

Priority Host Server Class TTL
10 faras.com. mx.zoho.com. IN 299
20 faras.com. mx2.zoho.com. IN 299
30 faras.com. mx3.zoho.com. IN 299

SOA Records

Domain Name Primary NS Responsible Email TTL
faras.com. ns-1083.awsdns-07.org. awsdns-hostmaster.amazon.com. 899

TXT Records

Host Value Class TTL
faras.com. v=spf1 IN 299

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 11th August, 2020
Content-Type: text/html; charset=UTF-8
Server: nginx/1.10.3 (Ubuntu)
Cache-Control: public, max-age=0
Content-Length: 1799
Connection: keep-alive
X-Powered-By: Express
Accept-Ranges: bytes
Last-Modified: 6th August, 2020
ETag: W/"707-173c3b80600"
Vary: Accept-Encoding

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns-1083.awsdns-07.org
ns-1808.awsdns-34.co.uk
ns-32.awsdns-04.com
ns-738.awsdns-28.net
Full Whois: We're sorry, due to high demand on our WHOIS servers, your request cannot be processed. Please try your request again shortly.

Nameservers

Name IP Address
ns-1083.awsdns-07.org 205.251.196.59
ns-1808.awsdns-34.co.uk 205.251.199.16
ns-32.awsdns-04.com 205.251.192.32
ns-738.awsdns-28.net 205.251.194.226
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address