appfigures.com

appfigures.com is SSL secured

Free website and domain report on appfigures.com

Last Updated: 5th April, 2021 Update Now
Overview

Snoop Summary for appfigures.com

This is a free and comprehensive report about appfigures.com. The domain appfigures.com is currently hosted on a server located in Queens, New York in United States with the IP address 204.145.71.6, where the local currency is USD and English is the local language. Our records indicate that appfigures.com is owned/operated by Fileitup Media. Appfigures.com is expected to earn an estimated $39 USD per day from advertising revenue. The sale of appfigures.com would possibly be worth $28,766 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Appfigures.com is very popular with an estimated 9,315 daily unique visitors. This report was last updated 5th April, 2021.

About appfigures.com

Site Preview: appfigures.com appfigures.com
Title: Appfigures - ASO tools, App Intelligence, and Analytics
Description: Grow you download with simple ASO tools, app intelligence, and comprehensive app analytics for all of your mobile apps.
Keywords and Tags: hardware, software
Related Terms: app nearpod, calendarwiz app, ccavenue app, doramasmp4 app, headspace app, ltt floatplane app, momo app, mygov app, nowgoal com app, quip app
Fav Icon:
Age: Over 15 years old
Domain Created: 14th March, 2009
Domain Updated: 15th March, 2021
Domain Expires: 14th March, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$28,766 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 46,984
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: 9,315
Monthly Visitors: 283,519
Yearly Visitors: 3,399,975
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $39 USD
Monthly Revenue: $1,199 USD
Yearly Revenue: $14,378 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: appfigures.com 14
Domain Name: appfigures 10
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.35 seconds
Load Time Comparison: Faster than 35% of sites

PageSpeed Insights

Avg. (All Categories) 76
Performance 93
Accessibility 63
Best Practices 80
SEO 73
Progressive Web App 73
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://appfigures.com/
Updated: 5th April, 2021

1.61 seconds
First Contentful Paint (FCP)
54%
39%
7%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
93

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 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).
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.9 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
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 appfigures.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 Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://appfigures.com/
http/1.1
0
58.028999999806
161
0
301
https://appfigures.com/
http/1.1
58.719000000565
264.47400000325
12228
47240
200
text/html
Document
https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300;0,400;0,600;0,700;0,800;1,400;1,600&family=Inter:wght@600;700;800&display=swap
h2
284.47600000072
301.9340000028
1883
22654
200
text/css
Stylesheet
https://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
h2
284.78600000381
377.77099999948
28957
199066
200
text/css
Stylesheet
https://d3v5ifbwser207.cloudfront.net/gs/group-content.css?cdc1b088714ebf4dd2cca5ce0bdfe3cd
h2
285.05199999927
361.18500000157
855
599
200
text/css
Stylesheet
https://d3v5ifbwser207.cloudfront.net/gs/group-content-new.css?2e982a784f32fa10e261c8c45e10f0db
h2
285.40300000168
365.55000000226
4597
26247
200
text/css
Stylesheet
https://d3v5ifbwser207.cloudfront.net/gs/group-home-new.css?20888731d718f8bde2858cc47faa5176
h2
285.72400000121
366.28000000201
6021
46245
200
text/css
Stylesheet
https://appfigures.com/new-design/images/menu/appfigures-logo_2x.png
http/1.1
288.62300000037
472.20100000413
2096
1627
200
image/png
Image
https://appfigures.com/images/pixel.gif
http/1.1
288.8329999987
471.73599999951
510
43
200
image/gif
Image
https://d3v5ifbwser207.cloudfront.net/scripts/utils/afkeys.js?6fd6e6da1ca56a49a3d776b50bf556f2
h2
287.50800000125
379.25600000017
1441
1913
200
application/javascript
Script
https://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
h2
287.98300000199
445.90900000185
74960
260632
200
application/javascript
Script
https://d3v5ifbwser207.cloudfront.net/gs/group-home.js?5ec7aa3b7e74aaebe468f89149496866
h2
288.21400000015
367.77100000472
791
233
200
application/javascript
Script
https://d3v5ifbwser207.cloudfront.net/gs/group-content-bottom-new.js?024079f5ce7a1fcbbd1f2c428f225e9f
h2
288.4120000017
363.14400000265
2624
5545
200
application/javascript
Script
https://d3v5ifbwser207.cloudfront.net/images/menu/support.png
h2
399.25000000221
470.38600000087
4268
3778
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo13.png
h2
402.65000000363
544.00100000203
10745
10258
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo5.png
h2
402.90800000366
420.62900000019
850
361
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo8.png
h2
403.20800000336
422.55300000397
1755
1265
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo4.png
h2
403.65200000087
543.28499999974
7134
6648
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo7.png
h2
403.98799999821
449.68900000094
1085
596
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo11.png
h2
404.30100000231
479.49900000094
6646
6155
200
image/png
Image
https://fonts.gstatic.com/s/inter/v3/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
h2
412.10300000239
416.48400000122
37500
36936
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
h2
412.38999999769
415.77700000198
9695
9132
200
font/woff2
Font
https://d3v5ifbwser207.cloudfront.net/fonts/main/icon.5.ttf
h2
412.91300000012
472.66700000182
22683
22184
200
application/octet-stream
Font
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
h2
413.13800000353
417.32700000284
9743
9180
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
h2
413.36500000034
416.91400000127
9642
9080
200
font/woff2
Font
https://client.crisp.chat/l.js
h2
476.66700000264
505.44900000386
3715
7802
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
569.96900000377
574.62900000246
20093
48759
200
text/javascript
Script
https://appfigures.com/new-design/images/menu/universal-analytics-icon.svg
http/1.1
609.03500000131
777.8479999979
1755
1282
200
image/svg+xml
Image
https://appfigures.com/new-design/images/menu/app-store-optimization-icon.svg
http/1.1
609.58000000392
716.33999999904
1586
1113
200
image/svg+xml
Image
https://appfigures.com/new-design/images/menu/competitor-intelligence-icon.svg
http/1.1
609.73599999852
796.61599999963
1953
1480
200
image/svg+xml
Image
https://appfigures.com/new-design/images/menu/review-monitoring-icon.svg
http/1.1
609.87500000192
988.95400000038
1880
1407
200
image/svg+xml
Image
https://www.google-analytics.com/gtm/js?id=GTM-54SDWJ2&cid=1532303707.1617642534
h2
636.17700000032
667.40800000116
35473
88538
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j89&a=1293716880&t=pageview&_s=1&dl=https%3A%2F%2Fappfigures.com%2F&ul=en-us&de=UTF-8&dt=Appfigures%20-%20ASO%20tools%2C%20App%20Intelligence%2C%20and%20Analytics&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=aGBAAEADQAAAAC~&jid=1684431841&gjid=291068166&cid=1532303707.1617642534&tid=UA-8382447-1&_gid=1584287380.1617642534&_r=1&_slc=1&cd4=0&cd7=0&z=1356687307
h2
696.58599999821
700.15199999762
620
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j89&tid=UA-8382447-1&cid=1532303707.1617642534&jid=1684431841&gjid=291068166&_gid=1584287380.1617642534&_u=aGBAAEACQAAAAC~&z=2099513871
h2
703.49800000258
711.30300000368
690
1
200
text/plain
XHR
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)
299.019
10.899
314.287
8.373
410.278
8.544
419.391
85.115
523.826
43.04
568.546
55.348
625.053
9.261
644.273
22.899
706.68
7.388
714.496
13.265
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Appfigures.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Appfigures.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Appfigures.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Appfigures.com should consider minifying JS files.
Remove unused CSS — Potential savings of 25 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Appfigures.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://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
28957
26049
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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 210 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://appfigures.com/
206.751
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Appfigures.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://appfigures.com/
190
https://appfigures.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Appfigures.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
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.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 319 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
74960
https://fonts.gstatic.com/s/inter/v3/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
37500
https://www.google-analytics.com/gtm/js?id=GTM-54SDWJ2&cid=1532303707.1617642534
35473
https://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
28957
https://d3v5ifbwser207.cloudfront.net/fonts/main/icon.5.ttf
22683
https://www.google-analytics.com/analytics.js
20093
https://appfigures.com/
12228
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo13.png
10745
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
9743
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
9695
Avoids an excessive DOM size — 419 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
419
Maximum DOM Depth
img
13
Maximum Child Elements
17
Avoid chaining critical requests — 12 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Appfigures.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
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 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://appfigures.com/
184.244
5.551
1.988
https://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
52.489
36.59
6.748
Minimizes main-thread work — 0.4 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)
Style & Layout
115.643
Script Evaluation
88.275
Other
79.518
Rendering
34.571
Parse HTML & CSS
22.88
Script Parsing & Compilation
14.721
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 34 requests • 319 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
34
326635
Script
7
139097
Font
5
89263
Stylesheet
5
42313
Image
13
42263
Document
1
12228
Other
3
1471
Media
0
0
Third-party
26
304466
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)
68463
0
56186
0
690
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
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.0013158904520882
0.00056431134381165
0.00049974004579655
0.00033858680628699
p
0.00019910400239748
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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

Largest Contentful Paint — 1.5 s
The timing of the largest text or image that is painted.

Opportunities

Eliminate render-blocking resources — Potential savings of 490 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Appfigures.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://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300;0,400;0,600;0,700;0,800;1,400;1,600&family=Inter:wght@600;700;800&display=swap
1883
230
https://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
28957
270
Remove unused JavaScript — Potential savings of 77 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://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
74960
54384
https://www.google-analytics.com/gtm/js?id=GTM-54SDWJ2&cid=1532303707.1617642534
35473
24567

Diagnostics

Serve static assets with an efficient cache policy — 24 resources found
Appfigures.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://www.google-analytics.com/analytics.js
7200000
20093
https://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
86400000
74960
https://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
86400000
28957
https://d3v5ifbwser207.cloudfront.net/fonts/main/icon.5.ttf
86400000
22683
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo13.png
86400000
10745
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo4.png
86400000
7134
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo11.png
86400000
6646
https://d3v5ifbwser207.cloudfront.net/gs/group-home-new.css?20888731d718f8bde2858cc47faa5176
86400000
6021
https://d3v5ifbwser207.cloudfront.net/gs/group-content-new.css?2e982a784f32fa10e261c8c45e10f0db
86400000
4597
https://d3v5ifbwser207.cloudfront.net/images/menu/support.png
86400000
4268
https://client.crisp.chat/l.js
86400000
3715
https://d3v5ifbwser207.cloudfront.net/gs/group-content-bottom-new.js?024079f5ce7a1fcbbd1f2c428f225e9f
86400000
2624
https://appfigures.com/new-design/images/menu/appfigures-logo_2x.png
86400000
2096
https://appfigures.com/new-design/images/menu/competitor-intelligence-icon.svg
86400000
1953
https://appfigures.com/new-design/images/menu/review-monitoring-icon.svg
86400000
1880
https://appfigures.com/new-design/images/menu/universal-analytics-icon.svg
86400000
1755
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo8.png
86400000
1755
https://appfigures.com/new-design/images/menu/app-store-optimization-icon.svg
86400000
1586
https://d3v5ifbwser207.cloudfront.net/scripts/utils/afkeys.js?6fd6e6da1ca56a49a3d776b50bf556f2
86400000
1441
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo7.png
86400000
1085
https://d3v5ifbwser207.cloudfront.net/gs/group-content.css?cdc1b088714ebf4dd2cca5ce0bdfe3cd
86400000
855
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo5.png
86400000
850
https://d3v5ifbwser207.cloudfront.net/gs/group-home.js?5ec7aa3b7e74aaebe468f89149496866
86400000
791
https://appfigures.com/images/pixel.gif
86400000
510

Diagnostics

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
63

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of appfigures.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.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<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.
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 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"]`
Appfigures.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Navigation

Heading elements are not 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.
Failing Elements

Internationalization and localization

`<html>` element does not have 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.
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
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.
80

Best Practices

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

Audits

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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

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 `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
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
>= 2.0.0 & <= 2.3.2
jQuery
Underscore
1.4.4
Moment.js
2.2.0
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

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 Request Resolution
http://appfigures.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 3 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
3
Medium
73

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for appfigures.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 appfigures.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.
Document has 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.
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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links do not have descriptive text — 7 links found
Make use of descriptive link text to assist search engines in understanding the 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

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.

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.
73

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 appfigures.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

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.
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 appfigures.com on mobile screens.
Provides 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.

PWA Optimized

Does not register 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.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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) 72
Performance 60
Accessibility 63
Best Practices 80
SEO 82
Progressive Web App 75
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://appfigures.com/
Updated: 5th April, 2021

2.53 seconds
First Contentful Paint (FCP)
33%
54%
13%

0.03 seconds
First Input Delay (FID)
95%
5%
0%

Simulate loading on mobile
60

Performance

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

Metrics

Total Blocking Time — 190 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).
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

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 appfigures.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 Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://appfigures.com/
http/1.1
0
41.840999998385
176
0
301
https://appfigures.com/
http/1.1
42.416999989655
2982.2759999952
12224
47240
200
text/html
Document
https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300;0,400;0,600;0,700;0,800;1,400;1,600&family=Inter:wght@600;700;800&display=swap
h2
2999.4770000048
3013.5190000001
1883
22654
200
text/css
Stylesheet
https://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
h2
2999.6729999839
3031.8499999994
28957
199066
200
text/css
Stylesheet
https://d3v5ifbwser207.cloudfront.net/gs/group-content.css?cdc1b088714ebf4dd2cca5ce0bdfe3cd
h2
2999.8369999812
3094.2639999848
855
599
200
text/css
Stylesheet
https://d3v5ifbwser207.cloudfront.net/gs/group-content-new.css?2e982a784f32fa10e261c8c45e10f0db
h2
3000.1029999985
3048.924999981
4597
26247
200
text/css
Stylesheet
https://d3v5ifbwser207.cloudfront.net/gs/group-home-new.css?20888731d718f8bde2858cc47faa5176
h2
3000.2969999914
3038.6810000055
6021
46245
200
text/css
Stylesheet
https://appfigures.com/new-design/images/menu/appfigures-logo_2x.png
http/1.1
3003.1199999794
3111.8469999928
2096
1627
200
image/png
Image
https://appfigures.com/images/pixel.gif
http/1.1
3003.3159999875
3111.3239999977
510
43
200
image/gif
Image
https://d3v5ifbwser207.cloudfront.net/scripts/utils/afkeys.js?6fd6e6da1ca56a49a3d776b50bf556f2
h2
3002.4369999883
3050.6889999961
1441
1913
200
application/javascript
Script
https://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
h2
3002.7659999905
3077.8120000032
74960
260632
200
application/javascript
Script
https://d3v5ifbwser207.cloudfront.net/gs/group-home.js?5ec7aa3b7e74aaebe468f89149496866
h2
3002.9079999949
3023.9059999876
791
233
200
application/javascript
Script
https://d3v5ifbwser207.cloudfront.net/gs/group-content-bottom-new.js?024079f5ce7a1fcbbd1f2c428f225e9f
h2
3003.0049999768
3022.1109999984
2624
5545
200
application/javascript
Script
https://client.crisp.chat/l.js
h2
3098.1179999944
3134.8299999954
3715
7802
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
3127.8919999895
3131.7789999885
20093
48759
200
text/javascript
Script
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo1_2x.png
h2
3140.2769999986
3159.2549999768
1992
1502
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo13_2x.png
h2
3140.5419999792
3189.0609999828
10750
10258
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo3_2x.png
h2
3140.7670000044
3174.96199999
1586
1097
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo10_2x.png
h2
3141.1640000006
3160.1300000038
3883
3394
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo4_2x.png
h2
3141.478000005
3174.4769999932
7138
6648
200
image/png
Image
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo5_2x.png
h2
3141.9339999848
3159.6140000038
902
413
200
image/png
Image
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
h2
3149.1659999883
3152.6989999984
9695
9132
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
h2
3149.7359999921
3152.294999978
9743
9180
200
font/woff2
Font
https://fonts.gstatic.com/s/inter/v3/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
h2
3150.0430000015
3153.1919999979
37499
36936
200
font/woff2
Font
https://appfigures.com/new-design/images/menu/universal-analytics-icon.svg
http/1.1
3233.6009999854
3336.8759999867
1755
1282
200
image/svg+xml
Image
https://appfigures.com/new-design/images/menu/app-store-optimization-icon.svg
http/1.1
3233.7520000001
3341.6579999903
1586
1113
200
image/svg+xml
Image
https://appfigures.com/new-design/images/menu/competitor-intelligence-icon.svg
http/1.1
3233.9299999876
3361.8529999803
1953
1480
200
image/svg+xml
Image
https://appfigures.com/new-design/images/menu/review-monitoring-icon.svg
http/1.1
3234.6939999843
3341.2090000056
1880
1407
200
image/svg+xml
Image
https://www.google-analytics.com/gtm/js?id=GTM-54SDWJ2&cid=453720549.1617642553
h2
3297.6379999891
3315.7669999928
35473
88538
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j89&a=2056362039&t=pageview&_s=1&dl=https%3A%2F%2Fappfigures.com%2F&ul=en-us&de=UTF-8&dt=Appfigures%20-%20ASO%20tools%2C%20App%20Intelligence%2C%20and%20Analytics&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=aGBAAEADQAAAAC~&jid=713456575&gjid=1197776912&cid=453720549.1617642553&tid=UA-8382447-1&_gid=2053950484.1617642553&_r=1&_slc=1&cd4=0&cd7=0&z=1574463027
h2
3342.0449999976
3345.8689999825
620
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j89&tid=UA-8382447-1&cid=453720549.1617642553&jid=713456575&gjid=1197776912&_gid=2053950484.1617642553&_u=aGBAAEACQAAAAC~&z=174312911
h2
3351.9229999802
3356.8939999968
690
1
200
text/plain
XHR
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)
3015.934
8.407
3028.489
7.462
3063.225
6.496
3125.929
113.691
3239.636
9.265
3264.571
38.715
3307.613
20.294
3327.952
7.869
3353.156
6.808
3360.456
11.361
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Appfigures.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Appfigures.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Appfigures.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Appfigures.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
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Appfigures.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://appfigures.com/
630
https://appfigures.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Appfigures.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
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.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 281 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
74960
https://fonts.gstatic.com/s/inter/v3/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
37499
https://www.google-analytics.com/gtm/js?id=GTM-54SDWJ2&cid=453720549.1617642553
35473
https://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
28957
https://www.google-analytics.com/analytics.js
20093
https://appfigures.com/
12224
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo13_2x.png
10750
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
9743
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
9695
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo4_2x.png
7138
Avoids an excessive DOM size — 419 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
419
Maximum DOM Depth
img
13
Maximum Child Elements
17
Avoid chaining critical requests — 11 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Appfigures.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
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.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://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
425.016
133.784
27.024
https://appfigures.com/
365.7
16.996
6.876
Unattributable
151.656
5.024
0.784
https://www.google-analytics.com/gtm/js?id=GTM-54SDWJ2&cid=453720549.1617642553
91.652
67.824
10.06
https://www.google-analytics.com/analytics.js
88.676
72.296
7.048
Minimizes main-thread work — 1.2 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)
Style & Layout
381.912
Script Evaluation
311.848
Other
254.728
Rendering
109.428
Parse HTML & CSS
85.176
Script Parsing & Compilation
58.464
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 31 requests • 281 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
31
288088
Script
7
139097
Font
3
56937
Stylesheet
5
42313
Image
12
36031
Document
1
12224
Other
3
1486
Media
0
0
Third-party
23
265908
Minimize third-party usage — Third-party code blocked the main thread for 20 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)
56186
20.488
58820
0
690
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00160615525421
0.00074467198149738
0.00036503528504773
0.00032935308593432
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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://d3v5ifbwser207.cloudfront.net/scripts/utils/afkeys.js?6fd6e6da1ca56a49a3d776b50bf556f2
3540
227
https://www.google-analytics.com/analytics.js
4697
81
https://appfigures.com/
1140
77
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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 — 3.5 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.6 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 4.5 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 230 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 3.5 s
The time taken for the primary content of the page to be rendered.

Opportunities

Remove unused CSS — Potential savings of 26 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Appfigures.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://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
28957
26324
Remove unused JavaScript — Potential savings of 77 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://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
74960
54240
https://www.google-analytics.com/gtm/js?id=GTM-54SDWJ2&cid=453720549.1617642553
35473
24567

Diagnostics

Serve static assets with an efficient cache policy — 22 resources found
Appfigures.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://www.google-analytics.com/analytics.js
7200000
20093
https://d3v5ifbwser207.cloudfront.net/gs/group-site-bottom.js?ef3a5112b691293401389f8711e020ac
86400000
74960
https://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
86400000
28957
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo13_2x.png
86400000
10750
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo4_2x.png
86400000
7138
https://d3v5ifbwser207.cloudfront.net/gs/group-home-new.css?20888731d718f8bde2858cc47faa5176
86400000
6021
https://d3v5ifbwser207.cloudfront.net/gs/group-content-new.css?2e982a784f32fa10e261c8c45e10f0db
86400000
4597
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo10_2x.png
86400000
3883
https://client.crisp.chat/l.js
86400000
3715
https://d3v5ifbwser207.cloudfront.net/gs/group-content-bottom-new.js?024079f5ce7a1fcbbd1f2c428f225e9f
86400000
2624
https://appfigures.com/new-design/images/menu/appfigures-logo_2x.png
86400000
2096
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo1_2x.png
86400000
1992
https://appfigures.com/new-design/images/menu/competitor-intelligence-icon.svg
86400000
1953
https://appfigures.com/new-design/images/menu/review-monitoring-icon.svg
86400000
1880
https://appfigures.com/new-design/images/menu/universal-analytics-icon.svg
86400000
1755
https://appfigures.com/new-design/images/menu/app-store-optimization-icon.svg
86400000
1586
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo3_2x.png
86400000
1586
https://d3v5ifbwser207.cloudfront.net/scripts/utils/afkeys.js?6fd6e6da1ca56a49a3d776b50bf556f2
86400000
1441
https://d3v5ifbwser207.cloudfront.net/new-design/images/logos/logo5_2x.png
86400000
902
https://d3v5ifbwser207.cloudfront.net/gs/group-content.css?cdc1b088714ebf4dd2cca5ce0bdfe3cd
86400000
855
https://d3v5ifbwser207.cloudfront.net/gs/group-home.js?5ec7aa3b7e74aaebe468f89149496866
86400000
791
https://appfigures.com/images/pixel.gif
86400000
510

Metrics

Speed Index — 6.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 5.9 s
The timing of the largest text or image that is painted.

Opportunities

Eliminate render-blocking resources — Potential savings of 870 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Appfigures.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://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300;0,400;0,600;0,700;0,800;1,400;1,600&family=Inter:wght@600;700;800&display=swap
1883
780
https://d3v5ifbwser207.cloudfront.net/gs/group-site-new.css?dba5b5e63d6d9a80ad53c46c3cf6075e
28957
1080
https://d3v5ifbwser207.cloudfront.net/gs/group-home-new.css?20888731d718f8bde2858cc47faa5176
6021
150
Reduce initial server response time — Root document took 2,940 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://appfigures.com/
2940.855

Diagnostics

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif
https://appfigures.com/images/pixel.gif
img
https://appfigures.com/images/pixel.gif

Other

First Contentful Paint (3G) — 6720 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
63

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of appfigures.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.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<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.
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 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"]`
Appfigures.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Navigation

Heading elements are not 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.
Failing Elements

Internationalization and localization

`<html>` element does not have 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.
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
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.
80

Best Practices

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

Audits

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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

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 `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
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
>= 2.0.0 & <= 2.3.2
jQuery
Underscore
1.4.4
Moment.js
2.2.0
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

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 Request Resolution
http://appfigures.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 3 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
3
Medium
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for appfigures.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 appfigures.com on mobile screens.
Document uses legible font sizes — 100% 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
100.00%
≥ 12px

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.
Document has 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.
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.
Links are 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.
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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 70% 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.
Tap Target Size Overlapping Target
67x21
67x21
109x21
79x21
105x21
123x21
57x21
57x21
52x21

Content Best Practices

Links do not have descriptive text — 7 links found
Make use of descriptive link text to assist search engines in understanding the 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

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.
75

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 appfigures.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

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.
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 appfigures.com on mobile screens.
Provides 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.

PWA Optimized

Does not register 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.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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.
Hosting

Server Location

Server IP Address: 204.145.71.6
Continent: North America
Country: United States
United States Flag
Region: New York
City: Queens
Longitude: -73.8883
Latitude: 40.6994
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Atlantic Metro Communications II, Inc.
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.13.154.6
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 3.8/5
WOT Trustworthiness: 75/100
WOT Child Safety: 99/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: appfigures.com
Issued By: DigiCert SHA2 Extended Validation Server CA
Valid From: 5th March, 2021
Valid To: 5th April, 2022
Subject: CN = appfigures.com
O = Appfigures Inc.
L = New York
S = US
Hash: a796b401
Issuer: CN = DigiCert SHA2 Extended Validation Server CA
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 5118444200729619940724922182533128324
Serial Number (Hex): 03D9C6C8687E04E7F505EE7604C02084
Valid From: 5th March, 2024
Valid To: 5th April, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:3D:D3:50:A5:D6:A0:AD:EE:F3:4A:60:0A:65:D3:21:D4:F8:F8:D6:0F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/sha2-ev-server-g3.crl

Full Name:
URI:http://crl4.digicert.com/sha2-ev-server-g3.crl

Certificate Policies: Policy: 2.16.840.1.114412.2.1
Policy: 2.23.140.1.1
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2ExtendedValidationServerCA.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Mar 5 17:05:15.313 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:AF:85:F5:E8:8F:C0:19:23:5D:4F:DF:
6A:B9:17:2E:97:D3:8E:8B:46:C9:B1:1E:60:C4:D8:44:
01:93:FA:42:4A:02:20:57:9C:1E:D8:98:49:89:C4:0A:
7D:0B:6E:37:35:38:2E:01:8E:54:6D:A4:4E:B6:36:3A:
95:DC:8F:5E:B0:62:FB
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 22:45:45:07:59:55:24:56:96:3F:A1:2F:F1:F7:6D:86:
E0:23:26:63:AD:C0:4B:7F:5D:C6:83:5C:6E:E2:0F:02
Timestamp : Mar 5 17:05:15.268 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:6D:EF:80:3F:70:76:16:40:49:12:13:4F:
05:EE:93:92:42:77:8B:6B:0E:54:18:C8:A8:20:28:99:
AD:87:D6:1F:02:21:00:E4:70:69:DE:A9:D8:14:E7:3E:
17:81:A5:0E:05:79:CC:86:A6:D4:23:00:73:96:09:DE:
7D:10:F5:87:7E:77:3B
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:analytics.appfigures.com
DNS:explorer.appfigures.com
DNS:appfigures.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
appfigures.com. 204.145.71.6 IN 3599

NS Records

Host Nameserver Class TTL
appfigures.com. ns-1149.awsdns-15.org. IN 299
appfigures.com. ns-1810.awsdns-34.co.uk. IN 299
appfigures.com. ns-484.awsdns-60.com. IN 299
appfigures.com. ns-743.awsdns-28.net. IN 299

MX Records

Priority Host Server Class TTL
1 appfigures.com. aspmx.l.google.com. IN 3599
10 appfigures.com. alt3.aspmx.l.google.com. IN 3599
10 appfigures.com. alt4.aspmx.l.google.com. IN 3599
5 appfigures.com. alt1.aspmx.l.google.com. IN 3599
5 appfigures.com. alt2.aspmx.l.google.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
appfigures.com. ns-743.awsdns-28.net. support.appfigures.com. 899

TXT Records

Host Value Class TTL
appfigures.com. google-site-verification=ijLYKGp0L83d3kNbl9qLFP6xGTs50yJGuZiTZ-QwpVw IN 299
appfigures.com. google-site-verification=t--P15dNXNEA7ncuh4O1OwSD28JhEZFeteIkNk5jiTk IN 299
appfigures.com. v=spf1 IN 299

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Date: 5th April, 2021
Content-Length: 47240
Set-Cookie: *
Content-Security-Policy: frame-ancestors appfigures.reamaze.com
X-Xss-Protection: 1; mode=block
X-Content-Type-Optons: nosniff
X-Frame-Options: SAMEORIGIN

Whois Lookup

Created: 14th March, 2009
Changed: 15th March, 2021
Expires: 14th March, 2022
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns-1149.awsdns-15.org
ns-1810.awsdns-34.co.uk
ns-484.awsdns-60.com
ns-743.awsdns-28.net
Owner Organization: Fileitup Media
Owner State: New York
Owner Country: US
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=APPFIGURES.COM
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=APPFIGURES.COM
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=APPFIGURES.COM
Full Whois: Domain Name: APPFIGURES.COM
Registry Domain ID: 1547089932_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2021-03-15T09:55:14Z
Creation Date: 2009-03-14T12:43:05Z
Registrar Registration Expiration Date: 2022-03-14T12:43:05Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registrant Organization: Fileitup Media
Registrant State/Province: New York
Registrant Country: US
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=APPFIGURES.COM
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=APPFIGURES.COM
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=APPFIGURES.COM
Name Server: NS-484.AWSDNS-60.COM
Name Server: NS-743.AWSDNS-28.NET
Name Server: NS-1149.AWSDNS-15.ORG
Name Server: NS-1810.AWSDNS-34.CO.UK
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-04-05T17:08:50Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
ns-1149.awsdns-15.org 205.251.196.125
ns-1810.awsdns-34.co.uk 205.251.199.18
ns-484.awsdns-60.com 205.251.193.228
ns-743.awsdns-28.net 205.251.194.231
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address