myfirstly.com

myfirstly.com is SSL secured

Free website and domain report on myfirstly.com

Last Updated: 30th March, 2024
Overview

Snoop Summary for myfirstly.com

This is a free and comprehensive report about myfirstly.com. Our records indicate that myfirstly.com is owned/operated by Domain Protection Services, Inc.. Myfirstly.com has the potential to be earning an estimated $4 USD per day from advertising revenue. If myfirstly.com was to be sold it would possibly be worth $2,758 USD (based on the daily revenue potential of the website over a 24 month period). Myfirstly.com is quite popular with an estimated 1,321 daily unique visitors. This report was last updated 30th March, 2024.

About myfirstly.com

Site Preview: myfirstly.com myfirstly.com
Title: Firstly Mobile
Description:
Keywords and Tags: blogs, wiki
Related Terms:
Fav Icon:
Age: Over 5 years old
Domain Created: 20th February, 2019
Domain Updated: 21st January, 2024
Domain Expires: 20th February, 2025
Review

Snoop Score

2/5

Valuation

$2,758 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 641,558
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: 1,321
Monthly Visitors: 40,207
Yearly Visitors: 482,165
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $4 USD
Monthly Revenue: $115 USD
Yearly Revenue: $1,374 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: myfirstly.com 13
Domain Name: myfirstly 9
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 71
Performance 74
Accessibility 77
Best Practices 87
SEO 82
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
74

Performance

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

Metrics

Time to Interactive — 2.0 s
The time taken for the page to become fully interactive.
Total Blocking Time — 10 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.067
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 70 ms
Users could experience a delay when interacting with the page.
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://myfirstly.com/
http/1.1
0
46.84599977918
434
0
301
text/html
https://myfirstly.com/
h2
47.629999928176
107.44900000282
28627
28140
200
text/html
Document
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
h2
124.32599999011
186.25499983318
54079
53593
200
text/css
Stylesheet
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
h2
124.5789998211
1372.5639998447
60528
60053
200
text/css
Stylesheet
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
h2
124.87499997951
1602.7019999456
121653
121177
200
text/css
Stylesheet
https://myfirstly.com/css/theme/style.css?ver=5.4.2
h2
125.08499994874
216.80699987337
222584
222097
200
text/css
Stylesheet
https://myfirstly.com/css/theme/responsive.css?ver=all
h2
125.57799997739
342.77699980885
32827
32352
200
text/css
Stylesheet
https://myfirstly.com/css/theme/animations.css?ver=5.4.2
h2
126.01299979724
188.52099985816
7619
7134
200
text/css
Stylesheet
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
h2
126.52799999341
241.98900000192
481861
481374
200
text/css
Stylesheet
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
h2
126.91399990581
468.37499993853
97362
96873
200
application/javascript
Script
https://myfirstly.com/js/jquery/jquery-migrate.min.js?ver=1.4.1
h2
127.14499980211
328.54999997653
10545
10056
200
application/javascript
Script
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
h2
127.44899978861
189.79400000535
119887
119386
200
application/javascript
Script
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
h2
127.73299985565
412.26499993354
327490
327000
200
application/javascript
Script
https://myfirstly.com/img/Digital-Turbine.png
h2
1677.5349997915
1871.6619999614
3595
3120
200
image/png
Image
https://myfirstly.com/img/transparent.png
h2
1677.6789999567
1831.8749999162
596
122
200
image/png
Image
https://myfirstly.com/img/Digital-Turbine-Logo.png
h2
1677.8269999195
1782.7190000098
7647
7172
200
image/png
Image
https://fonts.googleapis.com/css?family=Roboto:700%2C400
h2
1374.0379998926
1380.0879998598
1377
4072
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto%3A100%2C100italic%2C300%2C300italic%2Cregular%2Citalic%2C500%2C500italic%2C700%2C700italic%2C900%2C900italic&ver=5.4.2
h2
1381.4169999678
1388.7139998842
1942
24649
200
text/css
Stylesheet
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
h2
1390.0689999573
1607.966999989
29599
29110
200
application/javascript
Script
https://myfirstly.com/js/theme/easing.js?ver=1.3
h2
1604.5259998646
1672.2789998166
8793
8305
200
application/javascript
Script
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
h2
1675.4619998392
1954.9639998004
66472
65983
200
application/javascript
Script
https://myfirstly.com/js/theme/owl.carousel.min.js?ver=1.3.3
h2
1675.6670000032
1852.6809997857
24379
23890
200
application/javascript
Script
https://myfirstly.com/js/theme/jquery.nanoscroller.min.js?ver=3.4.0
h2
1676.114999922
1758.0229998566
10592
10103
200
application/javascript
Script
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
h2
1676.4269999694
1866.314999992
29019
28530
200
application/javascript
Script
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
h2
1676.7109998036
1992.7540000062
92367
91878
200
application/javascript
Script
https://myfirstly.com/js/theme/template.js?ver=1.2
h2
1676.8959998153
1903.4589999355
26586
26097
200
application/javascript
Script
https://myfirstly.com/js/wp-embed.min.js?ver=5.4.2
h2
1677.0859998651
1765.6669998541
1922
1434
200
application/javascript
Script
https://myfirstly.com/js/js_composer/js_composer_front.min.js?ver=5.5
h2
1677.3329998832
1900.9069998283
20199
19710
200
application/javascript
Script
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1710.5929998215
1713.9019998722
11805
11048
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1710.833999794
1713.4399998467
11790
11032
200
font/woff2
Font
https://myfirstly.com/css/assets/loader.gif
h2
2102.3649999406
2190.1039998047
3020
2545
200
image/gif
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)
118.055
8.925
129.62
7.168
225.011
10.551
250.769
17.719
1610.632
6.186
1617.418
67.072
1684.507
24.294
1713.189
10.544
1723.913
10.419
1737.616
10.084
1967.583
13.057
2005.461
83.989
2089.6
22.313
2127.005
8.596
2174.347
43.569
2218.942
13.829
2281.241
6.093
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Properly size images
Images can slow down the page's load time. Myfirstly.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Myfirstly.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 71 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Myfirstly.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222584
36603
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121653
21030
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60528
9431
https://myfirstly.com/css/theme/responsive.css?ver=all
32827
6101
Minify JavaScript — Potential savings of 10 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Myfirstly.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://myfirstly.com/js/theme/template.js?ver=1.2
26586
5031
https://myfirstly.com/js/theme/easing.js?ver=1.3
8793
4900
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 60 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://myfirstly.com/
60.817
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Myfirstly.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://myfirstly.com/
190
https://myfirstly.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Myfirstly.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 — Potential savings of 21 KiB
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.
URL Potential Savings (Bytes)
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
21641
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 1,872 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
481861
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
327490
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222584
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121653
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
119887
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
97362
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
92367
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
66472
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60528
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
54079
Avoids an excessive DOM size — 139 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
139
Maximum DOM Depth
20
Maximum Child Elements
16
Avoid chaining critical requests — 24 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Myfirstly.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://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
195.564
95.705
2.422
https://myfirstly.com/
138.561
26.952
2.275
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
88.758
73.234
6.949
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
60.603
51.467
2.039
Minimizes main-thread work — 0.6 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
286.91
Other
104.669
Style & Layout
91.829
Parse HTML & CSS
60.144
Rendering
56.447
Script Parsing & Compilation
30.306
Keep request counts low and transfer sizes small — 31 requests • 1,872 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
1917196
Stylesheet
9
984470
Script
14
865212
Document
1
28627
Font
2
23595
Image
4
14858
Other
1
434
Media
0
0
Third-party
4
26914
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)
26914
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.049645390070922
0.010726675715416
0.0058544785920672
0.00077187957746568
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 — 1 long task 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://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
2020
67
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.

Opportunities

Reduce unused JavaScript — Potential savings of 438 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://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
327490
150631
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
92367
69637
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
119887
59554
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
66472
51095
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
97362
43242
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
29019
27732
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
29599
24291
https://myfirstly.com/js/theme/owl.carousel.min.js?ver=1.3.3
24379
22550

Metrics

First Contentful Paint — 2.0 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 2.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.4 s
The timing of the largest text or image that is painted.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 1,540 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Myfirstly.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://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
54079
120
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60528
80
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121653
200
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222584
240
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
481861
400
https://fonts.googleapis.com/css?family=Roboto:700%2C400
1377
230
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
97362
80
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
119887
80
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
327490
280
Reduce unused CSS — Potential savings of 937 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Myfirstly.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://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
481861
478997
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222584
218633
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121653
118241
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60528
57113
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
54079
54079
https://myfirstly.com/css/theme/responsive.css?ver=all
32827
32827
Enable text compression — Potential savings of 1,444 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
481374
436112
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
327000
243404
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222097
190611
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121177
102844
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
119386
74290
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
96873
63069
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
91878
61645
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
65983
47682
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60053
47415
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
53593
45950
https://myfirstly.com/css/theme/responsive.css?ver=all
32352
27160
https://myfirstly.com/
28140
21471
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
29110
21431
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
28530
20396
https://myfirstly.com/js/theme/template.js?ver=1.2
26097
19174
https://myfirstly.com/js/theme/owl.carousel.min.js?ver=1.3.3
23890
17425
https://myfirstly.com/js/js_composer/js_composer_front.min.js?ver=5.5
19710
14056
https://myfirstly.com/js/theme/jquery.nanoscroller.min.js?ver=3.4.0
10103
6783
https://myfirstly.com/js/theme/easing.js?ver=1.3
8305
6300
https://myfirstly.com/js/jquery/jquery-migrate.min.js?ver=1.4.1
10056
6042
https://myfirstly.com/css/theme/animations.css?ver=5.4.2
7134
5445

Diagnostics

Serve static assets with an efficient cache policy — 25 resources found
Myfirstly.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://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
0
481861
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
0
327490
https://myfirstly.com/css/theme/style.css?ver=5.4.2
0
222584
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
0
121653
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
0
119887
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
0
97362
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
0
92367
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
0
66472
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
0
60528
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
0
54079
https://myfirstly.com/css/theme/responsive.css?ver=all
0
32827
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
0
29599
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
0
29019
https://myfirstly.com/js/theme/template.js?ver=1.2
0
26586
https://myfirstly.com/js/theme/owl.carousel.min.js?ver=1.3.3
0
24379
https://myfirstly.com/js/js_composer/js_composer_front.min.js?ver=5.5
0
20199
https://myfirstly.com/js/theme/jquery.nanoscroller.min.js?ver=3.4.0
0
10592
https://myfirstly.com/js/jquery/jquery-migrate.min.js?ver=1.4.1
0
10545
https://myfirstly.com/js/theme/easing.js?ver=1.3
0
8793
https://myfirstly.com/img/Digital-Turbine-Logo.png
0
7647
https://myfirstly.com/css/theme/animations.css?ver=5.4.2
0
7619
https://myfirstly.com/img/Digital-Turbine.png
0
3595
https://myfirstly.com/css/assets/loader.gif
0
3020
https://myfirstly.com/js/wp-embed.min.js?ver=5.4.2
0
1922
https://myfirstly.com/img/transparent.png
0
596
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/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
3.309000050649
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
2.606000052765
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://myfirstly.com/img/Digital-Turbine.png
77

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of myfirstly.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.
`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.
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.
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"]`
Myfirstly.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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that myfirstly.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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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
jQuery
1.12.4
GreenSock JS
1.9.7
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://myfirstly.com/
Allowed
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
4
Medium
1
High
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for myfirstly.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 myfirstly.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.
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.

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

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

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

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

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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
Does not set 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
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) 59
Performance 15
Accessibility 75
Best Practices 80
SEO 85
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
15

Performance

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

Metrics

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

Opportunities

Properly size images
Images can slow down the page's load time. Myfirstly.com should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 2 KiB
Time to Interactive can be slowed down by resources on the page. Myfirstly.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://myfirstly.com/css/assets/loader.gif
2545
2545
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 100 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://myfirstly.com/
100.886
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Myfirstly.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://myfirstly.com/
630
https://myfirstly.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Myfirstly.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.
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 1,873 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
481861
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
327498
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222584
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121661
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
119887
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
97370
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
92375
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
66480
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60536
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
54079
Avoids an excessive DOM size — 139 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
139
Maximum DOM Depth
20
Maximum Child Elements
16
Avoid chaining critical requests — 24 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Myfirstly.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.
Keep request counts low and transfer sizes small — 31 requests • 1,873 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
1917580
Stylesheet
9
984703
Script
14
865316
Document
1
28627
Font
2
23595
Image
4
14890
Other
1
449
Media
0
0
Third-party
4
27123
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)
27123
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 — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.07885228857398
0.0186767578125
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 — 20 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://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
11610
1577
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
14866
1017
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
16246
608
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
9510
411
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
16921
409
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
8010
398
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
13187
379
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
15883
363
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
3660
356
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
13566
351
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
14529
337
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
17387
328
https://myfirstly.com/css/theme/responsive.css?ver=all
5310
322
https://myfirstly.com/
2040
315
Unattributable
630
301
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
17715
296
Unattributable
931
289
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
9921
221
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
14310
219
https://myfirstly.com/
1362
185
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.

Other

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://myfirstly.com/
http/1.1
0
90.363999828696
449
0
301
text/html
https://myfirstly.com/
h2
91.035000048578
190.92299975455
28627
28140
200
text/html
Document
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
h2
296.21999990195
391.99300017208
54079
53593
200
text/css
Stylesheet
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
h2
297.6979999803
392.94699998572
60536
60053
200
text/css
Stylesheet
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
h2
297.93900018558
403.46799977124
121661
121177
200
text/css
Stylesheet
https://myfirstly.com/css/theme/style.css?ver=5.4.2
h2
298.14600013196
399.51900020242
222584
222097
200
text/css
Stylesheet
https://myfirstly.com/css/theme/responsive.css?ver=all
h2
300.36700004712
395.07600013167
32835
32352
200
text/css
Stylesheet
https://myfirstly.com/css/theme/animations.css?ver=5.4.2
h2
300.90299993753
391.29599975422
7619
7134
200
text/css
Stylesheet
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
h2
301.25200003386
401.60600002855
481861
481374
200
text/css
Stylesheet
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
h2
301.5089998953
394.48700007051
97370
96873
200
application/javascript
Script
https://myfirstly.com/js/jquery/jquery-migrate.min.js?ver=1.4.1
h2
301.76000017673
392.46599981561
10553
10056
200
application/javascript
Script
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
h2
301.96599988267
393.67099991068
119887
119386
200
application/javascript
Script
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
h2
302.18200013041
397.22999976948
327498
327000
200
application/javascript
Script
https://myfirstly.com/img/Digital-Turbine.png
h2
1108.1509999931
1295.2080001123
3603
3120
200
image/png
Image
https://myfirstly.com/img/transparent.png
h2
1108.8609998114
1291.7300001718
604
122
200
image/png
Image
https://myfirstly.com/img/Digital-Turbine-Logo.png
h2
1109.4969999976
1290.0149999186
7655
7172
200
image/png
Image
https://fonts.googleapis.com/css?family=Roboto:700%2C400
h2
610.9039997682
694.82999993488
1424
4968
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto%3A100%2C100italic%2C300%2C300italic%2Cregular%2Citalic%2C500%2C500italic%2C700%2C700italic%2C900%2C900italic&ver=5.4.2
h2
611.07200011611
695.88200002909
2104
31026
200
text/css
Stylesheet
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
h2
708.26599979773
792.01299976557
29607
29110
200
application/javascript
Script
https://myfirstly.com/js/theme/easing.js?ver=1.3
h2
709.56199988723
792.80699975789
8801
8305
200
application/javascript
Script
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
h2
1101.2659999542
1294.6979999542
66480
65983
200
application/javascript
Script
https://myfirstly.com/js/theme/owl.carousel.min.js?ver=1.3.3
h2
1101.5429999679
1291.3529998623
24387
23890
200
application/javascript
Script
https://myfirstly.com/js/theme/jquery.nanoscroller.min.js?ver=3.4.0
h2
1105.5580000393
1294.1780001856
10600
10103
200
application/javascript
Script
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
h2
1105.7679997757
1292.1440000646
29027
28530
200
application/javascript
Script
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
h2
1105.9400001541
1391.9939999469
92375
91878
200
application/javascript
Script
https://myfirstly.com/js/theme/template.js?ver=1.2
h2
1106.14599986
1293.587999884
26594
26097
200
application/javascript
Script
https://myfirstly.com/js/wp-embed.min.js?ver=5.4.2
h2
1106.3230000436
1213.0289999768
1930
1434
200
application/javascript
Script
https://myfirstly.com/js/js_composer/js_composer_front.min.js?ver=5.5
h2
1106.5170001239
1212.3679998331
20207
19710
200
application/javascript
Script
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1409.8029998131
1490.5329998583
11805
11048
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1492.3669998534
1496.4959998615
11790
11032
200
font/woff2
Font
https://myfirstly.com/css/assets/loader.gif
h2
2403.2370001078
2492.7059998736
3028
2545
200
image/gif
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)
288.676
13.119
386.058
9.723
496.354
5.299
502.245
80.53
587.496
6.898
596.713
88.96
685.698
12.3
699.308
99.608
801.022
394.318
1195.359
205.44
1403.794
78.841
1490.931
110.263
1602.232
94.69
1699.178
87.753
1786.952
14.035
1805.816
75.222
1881.951
508.357
2390.511
109.663
2501.22
84.288
2594.602
90.638
2781.705
304.19
3085.995
22.55
3108.639
72.127
3184.968
11.049
3196.406
102.228
3694.002
5.11
3786.147
14.337
3800.555
81.93
3995.561
6.932
4185.307
6.185
4410.593
73.953
5180.964
12.797
5834.392
46.356
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Minify CSS — Potential savings of 71 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Myfirstly.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222584
36603
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121661
21032
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60536
9433
https://myfirstly.com/css/theme/responsive.css?ver=all
32835
6103
Minify JavaScript — Potential savings of 10 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Myfirstly.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://myfirstly.com/js/theme/template.js?ver=1.2
26594
5032
https://myfirstly.com/js/theme/easing.js?ver=1.3
8801
4905
Avoid serving legacy JavaScript to modern browsers — Potential savings of 21 KiB
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.
URL Potential Savings (Bytes)
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
21647

Metrics

First Contentful Paint — 11.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 12.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 14.6 s
The timing of the largest text or image that is painted.
Time to Interactive — 17.8 s
The time taken for the page to become fully interactive.
Total Blocking Time — 4,950 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

Max Potential First Input Delay — 1,580 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 12.5 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 24137 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 10,390 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Myfirstly.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://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
54079
750
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60536
750
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121661
900
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222584
1050
https://myfirstly.com/css/theme/responsive.css?ver=all
32835
150
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
481861
2400
https://fonts.googleapis.com/css?family=Roboto:700%2C400
1424
780
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
97370
450
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
119887
600
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
327498
1950
Reduce unused CSS — Potential savings of 937 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Myfirstly.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://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
481861
479309
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222584
218758
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121661
118629
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60536
57121
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
54079
54079
https://myfirstly.com/css/theme/responsive.css?ver=all
32835
31566
Reduce unused JavaScript — Potential savings of 437 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://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
327498
149805
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
92375
69643
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
119887
59617
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
66480
51101
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
97370
43208
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
29027
27740
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
29607
24298
https://myfirstly.com/js/theme/owl.carousel.min.js?ver=1.3.3
24387
22558
Enable text compression — Potential savings of 1,444 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
481374
436112
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
327000
243404
https://myfirstly.com/css/theme/style.css?ver=5.4.2
222097
190611
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
121177
102844
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
119386
74290
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
96873
63069
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
91878
61645
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
65983
47682
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
60053
47415
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
53593
45950
https://myfirstly.com/css/theme/responsive.css?ver=all
32352
27160
https://myfirstly.com/
28140
21471
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
29110
21431
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
28530
20396
https://myfirstly.com/js/theme/template.js?ver=1.2
26097
19174
https://myfirstly.com/js/theme/owl.carousel.min.js?ver=1.3.3
23890
17425
https://myfirstly.com/js/js_composer/js_composer_front.min.js?ver=5.5
19710
14056
https://myfirstly.com/js/theme/jquery.nanoscroller.min.js?ver=3.4.0
10103
6783
https://myfirstly.com/js/theme/easing.js?ver=1.3
8305
6300
https://myfirstly.com/js/jquery/jquery-migrate.min.js?ver=1.4.1
10056
6042
https://myfirstly.com/css/theme/animations.css?ver=5.4.2
7134
5445

Diagnostics

Serve static assets with an efficient cache policy — 25 resources found
Myfirstly.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://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
0
481861
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
0
327498
https://myfirstly.com/css/theme/style.css?ver=5.4.2
0
222584
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
0
121661
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
0
119887
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
0
97370
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
0
92375
https://myfirstly.com/js/theme/select2.min.js?ver=3.5.1
0
66480
https://myfirstly.com/css/revslider/rs6.css?ver=6.2.23
0
60536
https://myfirstly.com/css/block-library/style.min.css?ver=5.4.2
0
54079
https://myfirstly.com/css/theme/responsive.css?ver=all
0
32835
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
0
29607
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
0
29027
https://myfirstly.com/js/theme/template.js?ver=1.2
0
26594
https://myfirstly.com/js/theme/owl.carousel.min.js?ver=1.3.3
0
24387
https://myfirstly.com/js/js_composer/js_composer_front.min.js?ver=5.5
0
20207
https://myfirstly.com/js/theme/jquery.nanoscroller.min.js?ver=3.4.0
0
10600
https://myfirstly.com/js/jquery/jquery-migrate.min.js?ver=1.4.1
0
10553
https://myfirstly.com/js/theme/easing.js?ver=1.3
0
8801
https://myfirstly.com/img/Digital-Turbine-Logo.png
0
7655
https://myfirstly.com/css/theme/animations.css?ver=5.4.2
0
7619
https://myfirstly.com/img/Digital-Turbine.png
0
3603
https://myfirstly.com/css/assets/loader.gif
0
3028
https://myfirstly.com/js/wp-embed.min.js?ver=5.4.2
0
1930
https://myfirstly.com/img/transparent.png
0
604
Reduce JavaScript execution time — 6.0 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://myfirstly.com/
3399.792
953.872
13.716
https://myfirstly.com/js/revslider/rs6.min.js?ver=6.2.23
2114.204
2008.944
30.532
https://myfirstly.com/js/revslider/rbtools.min.js?ver=6.2.23
1909.52
561.824
13.58
https://myfirstly.com/js/jquery/jquery.js?ver=1.12.4-wp
1679.484
952.748
336.556
Unattributable
895.152
31.516
0.916
https://myfirstly.com/css/js_composer/js_composer.min.css?ver=5.5
398.432
0
0
https://myfirstly.com/js/theme/bootstrap.min.js?ver=3.1.1
361.792
21.952
339.108
https://myfirstly.com/css/theme/bootstrap.css?ver=5.4.2
355.84
0
0
https://myfirstly.com/css/theme/responsive.css?ver=all
322.12
0
0
https://myfirstly.com/js/theme/jquery.mixitup.min.js?ver=2.1.7
308.192
1.484
306.708
https://myfirstly.com/js/js_composer/js_composer_front.min.js?ver=5.5
305.204
291.868
13.336
https://myfirstly.com/js/theme/TweenMax.min.js?ver=1.0
97.904
82.688
10.128
Minimize main-thread work — 12.3 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
4940.188
Style & Layout
2419.612
Other
1692.284
Parse HTML & CSS
1535.44
Script Parsing & Compilation
1100.44
Rendering
606.876
Garbage Collection
13.18
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/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
80.730000045151
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
4.1290000081062
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://myfirstly.com/img/Digital-Turbine.png
75

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of myfirstly.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.
`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.
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.
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"]`
Myfirstly.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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that myfirstly.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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
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
jQuery
1.12.4
GreenSock JS
1.9.7
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://myfirstly.com/
Allowed
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
4
Medium
1
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://myfirstly.com/img/Digital-Turbine.png
226 x 46
226 x 46
452 x 92
https://myfirstly.com/img/Digital-Turbine-Logo.png
125 x 125
179 x 179
250 x 250
85

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for myfirstly.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 myfirstly.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
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.
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.

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

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

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

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

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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
Does not set 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
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.
Hosting

Server Location

Server IP Address: 13.225.195.5
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Amazon.com, Inc.
Registration

Domain Registrant

Private Registration: No
Name: Whois Agent
Organization: Domain Protection Services, Inc.
Country: US
City: Denver
State: CO
Post Code: 80201
Email:
Phone: +1.7208009072
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Name.com, Inc. 104.18.6.161
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: myfirstly.com
Issued By: Amazon RSA 2048 M01
Valid From: 24th September, 2023
Valid To: 21st October, 2024
Subject: CN = myfirstly.com
Hash: fd88c149
Issuer: CN = Amazon RSA 2048 M01
O = Amazon
S = US
Version: 2
Serial Number: 9099163049796634440666775105876882934
Serial Number (Hex): 06D86F6000E2A7D143C3445BE2FD75F6
Valid From: 24th September, 2024
Valid To: 21st October, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:81:B8:0E:63:8A:89:12:18:E5:FA:3B:3B:50:95:9F:E6:E5:90:13:85
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.r2m01.amazontrust.com/r2m01.crl

Certificate Policies: Policy: 2.23.140.1.2.1

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
Timestamp : Sep 24 07:40:56.432 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:40:4A:4F:65:EE:83:57:B6:E0:EB:35:E5:
49:B5:13:47:42:88:12:5A:9F:11:75:82:73:28:BE:12:
7D:B2:47:B3:02:21:00:E0:A5:E4:1A:EB:20:EF:1F:4D:
C9:74:96:F0:E2:64:7E:32:20:81:47:FD:76:40:51:A0:
86:B2:87:C2:F2:43:D7
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Sep 24 07:40:56.378 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:35:0A:C5:DA:28:6E:6A:C7:FC:44:E9:C8:
78:7E:F4:F3:0B:E3:84:CA:E9:B2:85:35:8B:CC:5B:82:
18:BE:78:4B:02:20:33:EE:BD:F9:BC:5C:44:C0:79:23:
2D:E1:37:D2:0D:24:80:36:98:85:3F:6D:77:3E:E2:8E:
4B:9F:AD:90:A2:16
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DA:B6:BF:6B:3F:B5:B6:22:9F:9B:C2:BB:5C:6B:E8:70:
91:71:6C:BB:51:84:85:34:BD:A4:3D:30:48:D7:FB:AB
Timestamp : Sep 24 07:40:56.304 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:F3:C9:D4:4F:32:B2:D4:66:30:4A:25:
BD:9C:6E:2F:5D:75:6E:34:AA:19:64:C4:8B:A4:23:B3:
B9:BC:6F:73:16:02:21:00:C6:B1:F5:7D:CE:CD:82:2F:
6B:5D:57:E3:A5:C0:43:97:13:B1:C6:5A:75:7E:97:13:
D0:63:1B:E5:DE:5F:8D:C4
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.myfirstly.com
DNS:myfirstly.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
myfirstly.com. 108.138.64.58 IN 60
myfirstly.com. 108.138.64.115 IN 60
myfirstly.com. 108.138.64.75 IN 60
myfirstly.com. 108.138.64.68 IN 60

NS Records

Host Nameserver Class TTL
myfirstly.com. ns-1472.awsdns-56.org. IN 21600
myfirstly.com. ns-1878.awsdns-42.co.uk. IN 21600
myfirstly.com. ns-863.awsdns-43.net. IN 21600
myfirstly.com. ns-96.awsdns-12.com. IN 21600

MX Records

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

SOA Records

Domain Name Primary NS Responsible Email TTL
myfirstly.com. ns-96.awsdns-12.com. awsdns-hostmaster.amazon.com. 900

TXT Records

Host Value Class TTL
myfirstly.com. google-site-verification=XoFwn2DoxiE-i272t2Blnl_OdYL3T_QPREIm-IgfZS8 IN 300

HTTP Response Headers

HTTP-Code: HTTP/2 200
content-type: text/html
server: AmazonS3
date: 30th March, 2024
content-length: 28140
last-modified: 12th November, 2020
x-amz-version-id: bY_pLZJTRiXGcYxRFnLi_8YTye69JMpo
accept-ranges: bytes
etag: "1357b20b769efe108d4729291bc6e8fc"
x-cache: Hit from cloudfront
via: 1.1 6e86c05ccf44b10b3a7071fb1573829a.cloudfront.net (CloudFront)
x-amz-cf-pop: YUL62-C1
x-amz-cf-id: M9l4jGYf6ckAsg_gtyhDublR9UDXwyVbxXcCF-_6aWr1xCBFdalWbw==

Whois Lookup

Created: 20th February, 2019
Changed: 21st January, 2024
Expires: 20th February, 2025
Registrar: Name.com, Inc.
Status: clientTransferProhibited
Nameservers: ns-1472.awsdns-56.org
ns-1878.awsdns-42.co.uk
ns-863.awsdns-43.net
ns-96.awsdns-12.com
Owner Name: Redacted For Privacy
Owner Organization: Domain Protection Services, Inc.
Owner Street: PO Box 1769
Owner Post Code: 80201
Owner City: Denver
Owner State: CO
Owner Country: US
Owner Phone: +1.7208009072
Owner Email: https://www.name.com/contact-domain-whois/myfirstly.com
Admin Name: Redacted For Privacy
Admin Organization: Domain Protection Services, Inc.
Admin Street: PO Box 1769
Admin Post Code: 80201
Admin City: Denver
Admin State: CO
Admin Country: US
Admin Phone: +1.7208009072
Admin Email: https://www.name.com/contact-domain-whois/myfirstly.com
Tech Name: Redacted For Privacy
Tech Organization: Domain Protection Services, Inc.
Tech Street: PO Box 1769
Tech Post Code: 80201
Tech City: Denver
Tech State: CO
Tech Country: US
Tech Phone: +1.7208009072
Tech Email: https://www.name.com/contact-domain-whois/myfirstly.com
Full Whois: Domain Name: MYFIRSTLY.COM
Registry Domain ID: 2362387897_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.name.com
Registrar URL: http://www.name.com
Updated Date: 2024-01-21T17:13:04Z
Creation Date: 2019-02-20T15:47:05Z
Registrar Registration Expiration Date: 2025-02-20T15:47:05Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Reseller:
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Redacted For Privacy
Registrant Organization: Domain Protection Services, Inc.
Registrant Street: PO Box 1769
Registrant City: Denver
Registrant State/Province: CO
Registrant Postal Code: 80201
Registrant Country: US
Registrant Phone: +1.7208009072
Registrant Fax: +1.7209758725
Registrant Email: https://www.name.com/contact-domain-whois/myfirstly.com
Registry Admin ID: Not Available From Registry
Admin Name: Redacted For Privacy
Admin Organization: Domain Protection Services, Inc.
Admin Street: PO Box 1769
Admin City: Denver
Admin State/Province: CO
Admin Postal Code: 80201
Admin Country: US
Admin Phone: +1.7208009072
Admin Fax: +1.7209758725
Admin Email: https://www.name.com/contact-domain-whois/myfirstly.com
Registry Tech ID: Not Available From Registry
Tech Name: Redacted For Privacy
Tech Organization: Domain Protection Services, Inc.
Tech Street: PO Box 1769
Tech City: Denver
Tech State/Province: CO
Tech Postal Code: 80201
Tech Country: US
Tech Phone: +1.7208009072
Tech Fax: +1.7209758725
Tech Email: https://www.name.com/contact-domain-whois/myfirstly.com
Name Server: ns-96.awsdns-12.com
Name Server: ns-863.awsdns-43.net
Name Server: ns-1878.awsdns-42.co.uk
Name Server: ns-1472.awsdns-56.org
DNSSEC: unSigned
Registrar Abuse Contact Email: abuse@name.com
Registrar Abuse Contact Phone: +1.7203101849
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-03-30T19:12:36Z <<<

For more information on Whois status codes, please visit https://icann.org/epp


The data in the Name.com, Inc. WHOIS database is provided by Name.com, Inc. for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Name.com, Inc. does not guarantee its accuracy. Users accessing the Name.com, Inc. WHOIS service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Name.com, Inc., except as reasonably necessary to register domain names or modify existing registrations. When using the Name.com, Inc. WHOIS service, please consider the following: the WHOIS service is not a replacement for standard EPP commands to the SRS service. WHOIS is not considered authoritative for registered domain objects. The WHOIS service may be scheduled for downtime during production or OT&E maintenance periods. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis, for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://www.name.com/layered-access-request . Name.com, Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.



Nameservers

Name IP Address
ns-1472.awsdns-56.org 205.251.197.192
ns-1878.awsdns-42.co.uk 205.251.199.86
ns-863.awsdns-43.net 205.251.195.95
ns-96.awsdns-12.com 205.251.192.96
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address