mycontentstore.com

mycontentstore.com is SSL secured

Free website and domain report on mycontentstore.com

Last Updated: 7th June, 2020 Update Now
Overview

Snoop Summary for mycontentstore.com

This is a free and comprehensive report about mycontentstore.com. The domain mycontentstore.com is currently hosted on a server located in United States with the IP address 199.188.200.108, where USD is the local currency and the local language is English. Mycontentstore.com has the potential to be earning an estimated $6 USD per day from advertising revenue. If mycontentstore.com was to be sold it would possibly be worth $4,381 USD (based on the daily revenue potential of the website over a 24 month period). Mycontentstore.com is quite popular with an estimated 2,101 daily unique visitors. This report was last updated 7th June, 2020.

About mycontentstore.com

Site Preview: mycontentstore.com mycontentstore.com
Title: Home - MyContentStore
Description:
Keywords and Tags: 4k video downloader 32 bit, apple error 1712, elitetime payroll, huggaroo reviews, leh local sightseeing
Related Terms:
Fav Icon:
Age: Over 5 years old
Domain Created: 13th March, 2020
Domain Updated: 13th March, 2020
Domain Expires: 13th March, 2021
Review

Snoop Score

2/5

Valuation

$4,381 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 274,967
Alexa Reach:
SEMrush Rank (US): 41,776,225
SEMrush Authority Score: 14
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 21 0
Traffic: 0 0
Cost: $0 USD $0 USD
Traffic

Visitors

Daily Visitors: 2,101
Monthly Visitors: 63,948
Yearly Visitors: 766,865
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $6 USD
Monthly Revenue: $182 USD
Yearly Revenue: $2,186 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 397
Referring Domains: 52
Referring IPs: 49
Mycontentstore.com has 397 backlinks according to SEMrush. 62% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve mycontentstore.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of mycontentstore.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: http://yoomark.com/index.php
Target: https://mycontentstore.com/winter-garden-how-to-achieve-the-perfect-winter-garden-structure/

2
Source: https://japan.steinberg.net/forums/memberlist.php?first_char=m&mode=searchuser&sd=d&sk=b
Target: https://mycontentstore.com/

3
Source: https://iftweb.ift-aft.org/home/iftweb/2012/03/05/major-updates-added
Target: https://mycontentstore.com/latest-fashionable-pakistani-dresses-for-sale-online-summer-collection-2020/

4
Source: http://djnecky-oleje.nafotil.cz/piste/
Target: https://mycontentstore.com/tik-tok-app-how-this-pandemic-has-affected-tik-tok/

5
Source: https://japan.steinberg.net/forums/memberlist.php?first_char=m&mode=searchuser&sd=d&sk=f
Target: https://mycontentstore.com/

Top Ranking Keywords (US)

1
Keyword: apple error 1712
Ranked Page: https://mycontentstore.com/quickbooks-error-1712-how-to-resolve-quickbooks-error-1712-issues/

2
Keyword: elitetime payroll
Ranked Page: https://mycontentstore.com/what-is-the-new-in-quickbooks-online-payroll-all-the-information/

3
Keyword: 4k video downloader 32 bit
Ranked Page: http://mycontentstore.com/tag/4k-video-downloader-32-bit/

4
Keyword: leh local sightseeing
Ranked Page: http://mycontentstore.com/tag/leh-local-sightseeing/

5
Keyword: huggaroo reviews
Ranked Page: http://mycontentstore.com/have-you-tried-huggaroos-sensory-weighted-lap-pad-itll-change-your-life/

Domain Analysis

Value Length
Domain: mycontentstore.com 18
Domain Name: mycontentstore 14
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

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

Performance

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

Metrics

Time to Interactive — 1.8 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.023
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.3 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive mycontentstore.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mycontentstore.com/
0
187.86400003592
243
0
301
text/html
https://mycontentstore.com/
188.14099999145
536.67900001165
32057
287027
200
text/html
Document
https://c0.wp.com/c/5.4.1/wp-includes/css/dist/block-library/style.min.css
553.69900004007
581.46499999566
7548
53593
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-newsletter/style.css?ver=10.2
553.89000003925
835.89799999027
2005
6504
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-composer/td-multi-purpose/style.css?ver=819b7f9b02b0195f80e3eab970f44973x
554.06200001016
838.64800003357
9566
69334
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Oswald%3A400%2C800%7COpen+Sans%3A300italic%2C400%2C400italic%2C600%2C600italic%2C700%2C800%7CRoboto%3A300%2C400%2C400italic%2C500%2C500italic%2C700%2C900%2C800&display=swap&ver=10.2
554.5390000334
578.33600003505
2979
38243
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
555.22700003348
935.43100001989
26313
154733
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
555.60300004436
1012.1590000344
45827
361812
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
555.95599999651
1029.2070000432
52098
635571
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/includes/demos/gadgets/demo_style.css?ver=10.2
556.25800002599
832.12199999252
1906
7818
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/css/tdb_less_front.css?ver=c8cba5620a72d5b299fa8f62aeca6adfx
556.41399999149
915.50699999789
12922
103755
200
text/css
Stylesheet
https://c0.wp.com/p/jetpack/8.4.2/css/jetpack.css
556.87600001693
580.17500001006
13002
74081
200
text/css
Stylesheet
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
557.34400002984
594.46700004628
33273
96873
200
application/javascript
Script
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery-migrate.min.js
557.46999999974
572.64399999985
4223
10056
200
application/javascript
Script
https://mycontentstore.com/wp-includes/js/wp-emoji-release.min.js?ver=5.4.1
1086.8870000122
1333.8119999971
5105
13901
200
application/x-javascript
Script
https://mycontentstore.com/wp-content/uploads/2020/05/logo-300x83.png
1087.0219999924
1251.3260000269
19748
19362
200
image/png
Image
https://mycontentstore.com/wp-content/uploads/2020/04/rec.jpg
1087.3100000317
1251.8109999946
46552
46165
200
image/jpeg
Image
https://c0.wp.com/c/5.4.1/wp-includes/js/underscore.min.js
1014.7330000182
1031.3880000031
6011
16154
200
application/javascript
Script
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/js/js_posts_autoload.min.js?ver=c8cba5620a72d5b299fa8f62aeca6adfx
1032.5470000389
1173.402000044
2370
5058
200
application/x-javascript
Script
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/js/tagdiv_theme.min.js?ver=10.2
1086.11199999
1344.8830000125
54111
229013
200
application/x-javascript
Script
https://c0.wp.com/c/5.4.1/wp-includes/js/comment-reply.min.js
1086.3760000211
1103.6240000394
1441
2420
200
application/javascript
Script
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/js/js_files_for_front.min.js?ver=c8cba5620a72d5b299fa8f62aeca6adfx
1086.6230000393
1339.7960000439
4105
13599
200
application/x-javascript
Script
https://c0.wp.com/c/5.4.1/wp-includes/js/wp-embed.min.js
1086.7730000173
1102.4719999987
1068
1434
200
application/javascript
Script
https://stats.wp.com/e-202023.js
1087.4150000163
1103.2330000307
3306
8972
200
application/javascript
Script
https://mycontentstore.com/wp-content/uploads/2020/04/12.jpg
1106.9140000036
1110.1849999977
126549
252176
200
image/jpeg
Image
1112.2320000432
1112.266000011
0
121
200
image/png
Image
https://mycontentstore.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?17
1118.065000046
1592.8720000084
67448
123488
200
application/font-woff
Font
https://fonts.gstatic.com/s/opensans/v17/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
1120.2940000221
1124.1170000285
9780
9132
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
1121.2410000153
1128.0430000043
11665
11016
200
font/woff2
Font
https://fonts.gstatic.com/s/oswald/v31/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYySUhiCXAA.woff
1122.3089999985
1125.6740000099
13320
12672
200
font/woff
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
1123.4220000333
1148.331000004
11705
11056
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmYUtfBBc4AMP6lQ.woff2
1124.5990000316
1127.2810000228
11661
11012
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
1124.8980000382
1127.0220000297
9728
9080
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem6YaGs126MiZpBA-UFUK0Zdc1GAK6b.woff2
1133.1920000375
1137.6710000332
10376
9728
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
1154.326000018
1156.7820000346
13329
12680
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
1161.2580000074
1163.9060000307
11669
11020
200
font/woff2
Font
1192.8010000265
1192.8499999922
0
114
200
image/png
Image
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
1226.4360000263
1237.2970000142
9828
9180
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN8rsOUuhpKKSTjw.woff2
1227.4160000379
1231.3560000039
9840
9192
200
font/woff2
Font
1253.1220000237
1253.1510000117
0
117
200
image/png
Image
1400.5440000328
1400.5919999909
0
111
200
image/png
Image
1423.1610000134
1423.1940000318
0
101
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v20/KFOjCnqEu92Fr1Mu51S7ACc6CsTYl4BO.woff2
1515.4160000384
1518.2370000402
13317
12668
200
font/woff2
Font
https://pixel.wp.com/g.gif?v=ext&j=1%3A8.4.2&blog=174219129&post=2366&tz=0&srv=mycontentstore.com&host=mycontentstore.com&ref=&fcp=1225&rand=0.6713435459782673
1549.0550000104
1563.6740000336
215
50
200
image/gif
Image
https://mycontentstore.com/wp-content/uploads/2020/04/charcoalo.jpg
1808.2150000264
1893.0939999991
5378
4992
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/05/Feature-Image-mycontentstorecom-3-485x360.jpg
1825.7000000449
1990.6579999952
25480
25093
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/05/bill-gates-biography.jpg
1843.9490000019
1929.0059999912
6107
5721
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/05/airport-taxi-cab-485x360.jpg
1861.7180000292
2024.8530000099
33309
32922
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/05/the-rise-of-e-commerce.jpg
1879.0600000066
1965.9310000134
11575
11188
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/04/cheap-dress-online-324x160.jpg
1902.8900000267
1991.0760000348
10520
10133
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/05/image-324x160.jpg
1939.2210000078
2103.6300000269
16047
15660
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/05/Abu-Dhabi-Movers-and-Packers-324x160.jpg
1980.1130000269
2064.6750000305
7693
7307
200
image/jpeg
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)
565.706
9.523
578.251
33.427
1040.041
13.847
1057.516
27.102
1085.133
30.09
1115.237
100.458
1235.83
41.491
1286.094
35.704
1323.732
18.745
1349.465
37.419
1392.022
32.03
1427.589
20.505
1451.357
10.259
1463.725
98.682
1562.443
8.534
1577.347
75.557
1656.631
68.446
1726.195
108.212
1983.291
5.169
2013.502
19.511
2033.043
5.322
2349.866
5.265
2433.266
5.326
2483.295
6.177
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Mycontentstore.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mycontentstore.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 30 KB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mycontentstore.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
52098
11459
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
45827
9168
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
26313
7283
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/css/tdb_less_front.css?ver=c8cba5620a72d5b299fa8f62aeca6adfx
12922
2705
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mycontentstore.com should consider minifying JS files.
Remove unused JavaScript — Potential savings of 62 KB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/js/tagdiv_theme.min.js?ver=10.2
54111
38605
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
33273
14165
https://c0.wp.com/c/5.4.1/wp-includes/js/underscore.min.js
6011
4482
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/js/js_files_for_front.min.js?ver=c8cba5620a72d5b299fa8f62aeca6adfx
4105
3793
https://stats.wp.com/e-202023.js
3306
2307
Efficiently encode images — Potential savings of 23 KB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://mycontentstore.com/wp-content/uploads/2020/04/rec.jpg
46165
23119
Serve images in next-gen formats — Potential savings of 41 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://mycontentstore.com/wp-content/uploads/2020/04/rec.jpg
46165
32589
https://mycontentstore.com/wp-content/uploads/2020/05/logo-300x83.png
19362
9022
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 350 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Mycontentstore.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://mycontentstore.com/
0
https://mycontentstore.com/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mycontentstore.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.

Diagnostics

Avoids enormous network payloads — Total size was 815 KB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://mycontentstore.com/wp-content/uploads/2020/04/12.jpg
126549
https://mycontentstore.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?17
67448
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/js/tagdiv_theme.min.js?ver=10.2
54111
https://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
52098
https://mycontentstore.com/wp-content/uploads/2020/04/rec.jpg
46552
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
45827
https://mycontentstore.com/wp-content/uploads/2020/05/airport-taxi-cab-485x360.jpg
33309
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
33273
https://mycontentstore.com/
32057
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
26313
Uses efficient cache policy on static assets — 0 resources found
Mycontentstore.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoid chaining critical requests — 30 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mycontentstore.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.2 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://mycontentstore.com/
624.316
42.527
7.597
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
222.47
151.333
1.596
Unattributable
67.067
1.279
1.002
Minimizes main-thread work — 1.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
453.88
Script Evaluation
218.399
Other
126.09
Rendering
125.425
Parse HTML & CSS
81.974
Script Parsing & Compilation
21.022
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 47 requests • 815 KB
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
47
834318
Image
12
309173
Font
13
203666
Stylesheet
10
174166
Script
10
115013
Document
1
32057
Other
1
243
Media
0
0
Third-party
22
209284
Minimize third-party usage — Third-party code blocked the main thread for 20 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
66566
19.356
139197
0
3521
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element
a
a
a
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.

Budgets

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

Metrics

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

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 440 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mycontentstore.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://c0.wp.com/c/5.4.1/wp-includes/css/dist/block-library/style.min.css
7548
270
https://mycontentstore.com/wp-content/plugins/td-newsletter/style.css?ver=10.2
2005
70
https://mycontentstore.com/wp-content/plugins/td-composer/td-multi-purpose/style.css?ver=819b7f9b02b0195f80e3eab970f44973x
9566
230
https://fonts.googleapis.com/css?family=Oswald%3A400%2C800%7COpen+Sans%3A300italic%2C400%2C400italic%2C600%2C600italic%2C700%2C800%7CRoboto%3A300%2C400%2C400italic%2C500%2C500italic%2C700%2C900%2C800&display=swap&ver=10.2
2979
230
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
26313
390
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
45827
550
https://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
52098
590
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/includes/demos/gadgets/demo_style.css?ver=10.2
1906
150
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/css/tdb_less_front.css?ver=c8cba5620a72d5b299fa8f62aeca6adfx
12922
150
https://c0.wp.com/p/jetpack/8.4.2/css/jetpack.css
13002
310
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
33273
510
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery-migrate.min.js
4223
150
Remove unused CSS — Potential savings of 139 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mycontentstore.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://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
52098
49286
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
45827
44255
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
26313
22630
https://c0.wp.com/p/jetpack/8.4.2/css/jetpack.css
13002
13002
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/css/tdb_less_front.css?ver=c8cba5620a72d5b299fa8f62aeca6adfx
12922
12896

Diagnostics

Avoid an excessive DOM size — 1,722 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
1,722
Maximum DOM Depth
20
Maximum Child Elements
59
74

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
Underscore
1.8.3
WordPress
5.4.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://mycontentstore.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 4 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
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mycontentstore.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 mycontentstore.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

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

Manual Checks

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

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

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 mycontentstore.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://mycontentstore.com/
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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
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) 69
Performance 54
Accessibility 83
Best Practices 77
SEO 83
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
54

Performance

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

Metrics

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

Other

Estimated Input Latency — 50 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive mycontentstore.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mycontentstore.com/
0
187.03000003006
259
0
301
text/html
https://mycontentstore.com/
187.29300005361
373.29699995462
32078
287027
200
text/html
Document
https://c0.wp.com/c/5.4.1/wp-includes/css/dist/block-library/style.min.css
392.15500000864
411.557000014
7548
53593
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-newsletter/style.css?ver=10.2
392.33199995942
516.89299999271
2005
6504
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-composer/td-multi-purpose/style.css?ver=819b7f9b02b0195f80e3eab970f44973x
392.6709999796
524.60999996401
9531
69334
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Oswald%3A400%2C800%7COpen+Sans%3A300italic%2C400%2C400italic%2C600%2C600italic%2C700%2C800%7CRoboto%3A300%2C400%2C400italic%2C500%2C500italic%2C700%2C900%2C800&display=swap&ver=10.2
393.18699995056
417.56600001827
3014
39453
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
393.41899997089
609.32899999898
26313
154733
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
393.58100004029
690.09399996139
45792
361812
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
393.72200006619
706.11100003589
52098
635571
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/includes/demos/gadgets/demo_style.css?ver=10.2
393.83700001054
515.21199999843
1872
7818
200
text/css
Stylesheet
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/css/tdb_less_front.css?ver=c8cba5620a72d5b299fa8f62aeca6adfx
393.96100002341
523.67999998387
12957
103755
200
text/css
Stylesheet
https://c0.wp.com/p/jetpack/8.4.2/css/jetpack.css
394.24699998926
427.12400003802
13002
74081
200
text/css
Stylesheet
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
394.731999957
428.11700003222
33273
96873
200
application/javascript
Script
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery-migrate.min.js
395.03699995112
410.81200004555
4223
10056
200
application/javascript
Script
https://mycontentstore.com/wp-includes/js/wp-emoji-release.min.js?ver=5.4.1
753.47800005693
838.9169999864
5105
13901
200
application/x-javascript
Script
https://mycontentstore.com/wp-content/uploads/2020/05/logo-300x83.png
753.75400006305
839.22500000335
19748
19362
200
image/png
Image
https://mycontentstore.com/wp-content/uploads/2020/04/rec.jpg
753.91500000842
1001.3230000623
46552
46165
200
image/jpeg
Image
https://c0.wp.com/c/5.4.1/wp-includes/js/underscore.min.js
692.99500004854
710.59599996079
6011
16154
200
application/javascript
Script
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/js/js_posts_autoload.min.js?ver=c8cba5620a72d5b299fa8f62aeca6adfx
709.24900006503
797.23200004082
2336
5058
200
application/x-javascript
Script
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/js/tagdiv_theme.min.js?ver=10.2
752.32400000095
931.20700004511
54076
229013
200
application/x-javascript
Script
https://c0.wp.com/c/5.4.1/wp-includes/js/comment-reply.min.js
752.73099995684
769.70099995378
1441
2420
200
application/javascript
Script
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/js/js_files_for_front.min.js?ver=c8cba5620a72d5b299fa8f62aeca6adfx
753.12899996061
837.98700000625
4139
13599
200
application/x-javascript
Script
https://c0.wp.com/c/5.4.1/wp-includes/js/wp-embed.min.js
753.28800000716
772.60300004855
1063
1434
200
application/javascript
Script
https://stats.wp.com/e-202023.js
754.18499996886
770.1909999596
3306
8972
200
application/javascript
Script
https://mycontentstore.com/wp-content/uploads/2020/04/12.jpg
775.58500005398
779.64099997189
126526
2017408
200
image/jpeg
Image
780.70300002582
780.7530000573
0
121
200
image/png
Image
https://mycontentstore.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?17
785.88800004218
1033.5679999553
67448
123488
200
application/font-woff
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
788.4919999633
791.47000005469
11705
11056
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmYUtfBBc4AMP6lQ.woff2
790.27200001292
793.46700001042
11661
11012
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
791.25899996143
793.9179999521
9728
9080
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
792.00300003868
794.62000005879
9780
9132
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem6YaGs126MiZpBA-UFUK0Zdc1GAK6b.woff2
798.98199997842
802.40200005937
10376
9728
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
819.73700004164
824.17100004386
11665
11016
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
824.80800000485
827.91400002316
13329
12680
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
831.01099997293
834.3589999713
11669
11020
200
font/woff2
Font
864.00499998126
864.04600006063
0
114
200
image/png
Image
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
896.71500003897
899.77000001818
9827
9180
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN8rsOUuhpKKSTjw.woff2
897.46700006071
944.15900006425
9840
9192
200
font/woff2
Font
949.78599995375
949.82900004834
0
117
200
image/png
Image
1181.6500000423
1181.6820000531
0
111
200
image/png
Image
1215.8660000423
1215.9110000357
0
101
200
image/png
Image
https://fonts.gstatic.com/s/oswald/v31/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiZSSShiA.woff2
1219.063000055
1222.6269999519
10420
9772
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v20/KFOjCnqEu92Fr1Mu51S7ACc6CsTYl4BO.woff2
1366.1749999737
1372.5169999525
13317
12668
200
font/woff2
Font
https://pixel.wp.com/g.gif?v=ext&j=1%3A8.4.2&blog=174219129&post=2366&tz=0&srv=mycontentstore.com&host=mycontentstore.com&ref=&fcp=877&rand=0.539137870398972
1407.0589999901
1422.7950000204
215
50
200
image/gif
Image
https://mycontentstore.com/wp-content/uploads/2020/05/bill-gates-biography.jpg
1612.7750000451
1698.5130000394
6107
5721
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/04/charcoalo.jpg
1629.8279999755
1717.0230000047
5378
4992
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/05/Feature-Image-mycontentstorecom-3-485x360.jpg
1653.8289999589
1817.6550000207
25480
25093
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/05/airport-taxi-cab-485x360.jpg
1689.5019999938
1861.3129999721
33309
32922
200
image/jpeg
Image
https://mycontentstore.com/wp-content/uploads/2020/05/the-rise-of-e-commerce.jpg
1730.16799998
1817.228000029
11575
11188
200
image/jpeg
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)
403.456
10.074
416.46
48.706
718.495
12.162
734.714
19.193
754.493
27.58
782.086
105.424
906.066
34.409
945.223
29.934
981.226
28.611
1012.089
16.664
1032.178
21.026
1055.606
17.755
1075.7
16.135
1094.887
40.275
1137.047
20.473
1159.19
20.211
1181.28
24.686
1209.298
31.881
1243.388
9.317
1255.82
160.394
1416.279
13.466
1435.544
76.464
1517.416
122.331
1862.5
8.818
2075.43
5.461
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Mycontentstore.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mycontentstore.com should consider lazy-loading offscreen and hidden images.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mycontentstore.com should consider minifying JS files.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 190 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Mycontentstore.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://mycontentstore.com/
0
https://mycontentstore.com/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mycontentstore.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.

Diagnostics

Avoids enormous network payloads — Total size was 778 KB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://mycontentstore.com/wp-content/uploads/2020/04/12.jpg
126526
https://mycontentstore.com/wp-content/themes/Newspaper/images/icons/newspaper.woff?17
67448
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/js/tagdiv_theme.min.js?ver=10.2
54076
https://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
52098
https://mycontentstore.com/wp-content/uploads/2020/04/rec.jpg
46552
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
45792
https://mycontentstore.com/wp-content/uploads/2020/05/airport-taxi-cab-485x360.jpg
33309
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
33273
https://mycontentstore.com/
32078
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
26313
Uses efficient cache policy on static assets — 0 resources found
Mycontentstore.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoid chaining critical requests — 30 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mycontentstore.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 — 1.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://mycontentstore.com/
2832.3
243.7
34.592
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
884.784
640.196
6.44
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/js/tagdiv_theme.min.js?ver=10.2
358.384
56.92
16.54
Unattributable
258.296
5.248
0.72
https://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
76.772
0
0
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 44 requests • 778 KB
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
44
797097
Image
9
274890
Font
13
200765
Stylesheet
10
174132
Script
10
114973
Document
1
32078
Other
1
259
Media
0
0
Third-party
22
206413
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
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.

Budgets

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

Metrics

Speed Index — 4.8 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 7.3 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 6.1 s
The time taken for the page's main thread to be quiet enough to handle input.

Opportunities

Minify CSS — Potential savings of 30 KB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mycontentstore.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
52098
11459
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
45792
9161
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
26313
7283
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/css/tdb_less_front.css?ver=c8cba5620a72d5b299fa8f62aeca6adfx
12957
2712
Remove unused JavaScript — Potential savings of 62 KB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/js/tagdiv_theme.min.js?ver=10.2
54076
38663
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
33273
14185
https://c0.wp.com/c/5.4.1/wp-includes/js/underscore.min.js
6011
4482
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/js/js_files_for_front.min.js?ver=c8cba5620a72d5b299fa8f62aeca6adfx
4139
3824
https://stats.wp.com/e-202023.js
3306
2307
Efficiently encode images — Potential savings of 23 KB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://mycontentstore.com/wp-content/uploads/2020/04/rec.jpg
46165
23119
Serve images in next-gen formats — Potential savings of 41 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://mycontentstore.com/wp-content/uploads/2020/04/rec.jpg
46165
32589
https://mycontentstore.com/wp-content/uploads/2020/05/logo-300x83.png
19362
9022

Metrics

First Contentful Paint — 4.2 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 7.5 s
The timing of the largest text or image that is painted.

Other

Max Potential First Input Delay — 320 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 4.2 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 8970 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 1,470 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mycontentstore.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://c0.wp.com/c/5.4.1/wp-includes/css/dist/block-library/style.min.css
7548
1230
https://mycontentstore.com/wp-content/plugins/td-newsletter/style.css?ver=10.2
2005
330
https://mycontentstore.com/wp-content/plugins/td-composer/td-multi-purpose/style.css?ver=819b7f9b02b0195f80e3eab970f44973x
9531
930
https://fonts.googleapis.com/css?family=Oswald%3A400%2C800%7COpen+Sans%3A300italic%2C400%2C400italic%2C600%2C600italic%2C700%2C800%7CRoboto%3A300%2C400%2C400italic%2C500%2C500italic%2C700%2C900%2C800&display=swap&ver=10.2
3014
930
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
26313
1830
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
45792
2580
https://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
52098
2730
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/includes/demos/gadgets/demo_style.css?ver=10.2
1872
630
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/css/tdb_less_front.css?ver=c8cba5620a72d5b299fa8f62aeca6adfx
12957
780
https://c0.wp.com/p/jetpack/8.4.2/css/jetpack.css
13002
1380
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
33273
2430
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery-migrate.min.js
4223
630
Remove unused CSS — Potential savings of 139 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mycontentstore.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://mycontentstore.com/wp-content/plugins/td-standard-pack/Newspaper/assets/css/td_standard_pack_main.css?ver=f3d6322e6f953bf07f46586e1d97917d
52098
49484
https://mycontentstore.com/wp-content/plugins/td-composer/legacy/Newspaper/assets/css/td_legacy_main.css?ver=819b7f9b02b0195f80e3eab970f44973x
45792
44055
https://mycontentstore.com/wp-content/themes/Newspaper/style.css?ver=10.2
26313
22521
https://c0.wp.com/p/jetpack/8.4.2/css/jetpack.css
13002
13002
https://mycontentstore.com/wp-content/plugins/td-cloud-library/assets/css/tdb_less_front.css?ver=c8cba5620a72d5b299fa8f62aeca6adfx
12957
12931

Diagnostics

Avoid an excessive DOM size — 1,722 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
1,722
Maximum DOM Depth
20
Maximum Child Elements
66
Minimize main-thread work — 4.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)
Style & Layout
2258.888
Script Evaluation
989
Other
519.092
Rendering
473.216
Parse HTML & CSS
298.568
Script Parsing & Compilation
83.724
Reduce the impact of third-party code — Third-party code blocked the main thread for 480 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)
66561
476.048
136331
0
3521
0
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://c0.wp.com/c/5.4.1/wp-includes/js/jquery/jquery.js
line: 2
83

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Names and labels

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
Underscore
1.8.3
WordPress
5.4.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://mycontentstore.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 4 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

Audits

Displays images with inappropriate size
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://mycontentstore.com/wp-content/uploads/2020/05/logo-300x83.png
173 x 48
300 x 83
455 x 126
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mycontentstore.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 mycontentstore.com on mobile screens.
Document uses legible font sizes — 91.23% 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
.td-module-meta-info
7.71%
11px
.td-post-category
0.91%
10px
0.14%
< 12px
91.23%
≥ 12px

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 82% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
83x15
83x15
83x15
83x15
72x15
83x15
83x15
72x15
72x15
83x15
83x15
72x15
83x15
83x15
83x15
32x19
60x19
106x19
41x19
60x19
94x19
44x19
76x19

Content Best Practices

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

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

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

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 mycontentstore.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://mycontentstore.com/
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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
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: 199.188.200.108
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Namecheap, Inc.
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
NameCheap, Inc. 104.19.251.10
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: mycontentstore.com
Issued By: Sectigo RSA Domain Validation Secure Server CA
Valid From: 13th March, 2020
Valid To: 13th March, 2021
Subject: CN = mycontentstore.com
Hash: a0ad2b01
Issuer: CN = Sectigo RSA Domain Validation Secure Server CA
O = Sectigo Limited
S = GB
Version: 2
Serial Number: 154755395991445635635052060789124357747
Serial Number (Hex): 746CCE1C507A5D4DCB2319D82B67DE73
Valid From: 13th March, 2025
Valid To: 13th March, 2025
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP - URI:http://ocsp.sectigo.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Mar 13 22:53:27.044 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:C1:E7:AB:F4:35:53:DC:0E:00:8E:42:
57:70:1A:BB:DA:7A:5A:22:1F:70:88:4C:65:11:8B:ED:
6F:4D:59:74:D8:02:20:26:80:14:E2:89:8C:3D:C1:CB:
7D:AF:D8:A3:3F:41:4C:52:AF:3E:D0:A1:01:94:34:92:
F9:B7:22:2F:16:A7:D3
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Mar 13 22:53:27.070 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:D4:55:C9:A7:13:B7:70:91:E3:82:F1:
AA:BC:2C:E0:49:6F:60:08:6E:CD:EC:3C:45:94:68:B8:
89:3C:33:B6:BC:02:21:00:9F:5D:13:C2:15:92:93:0C:
D6:B1:B2:CF:CE:0B:0B:F8:E6:70:2D:FE:13:AC:D6:81:
86:7C:5F:97:8A:D5:BB:B3
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.mycontentstore.com
DNS:mycontentstore.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
mycontentstore.com. 199.188.200.108 IN 1199

NS Records

Host Nameserver Class TTL
mycontentstore.com. dns1.namecheaphosting.com. IN 21599
mycontentstore.com. dns2.namecheaphosting.com. IN 21599

MX Records

Priority Host Server Class TTL
10 mycontentstore.com. smx1.web-hosting.com. IN 1199
20 mycontentstore.com. smx2.web-hosting.com. IN 1199
30 mycontentstore.com. smx3.web-hosting.com. IN 1199

SOA Records

Domain Name Primary NS Responsible Email TTL
mycontentstore.com. dns1.namecheaphosting.com. cpanel.tech.namecheap.com. 21599

TXT Records

Host Value Class TTL
mycontentstore.com. MAltYWlsLm15Y29udGVudHN0b3JlLmNvbS4K IN 1199
mycontentstore.com. v=spf1 IN 1199

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 7th June, 2020
Server: Apache
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/7.2.31
Link: <https://mycontentstore.com/wp-json/>; rel="https://api.w.org/", <https://mycontentstore.com/>; rel=shortlink
Content-Security-Policy: upgrade-insecure-requests
Referrer-Policy: no-referrer-when-downgrade

Whois Lookup

Created: 13th March, 2020
Changed: 13th March, 2020
Expires: 13th March, 2021
Registrar: NameCheap, Inc.
Status: clientTransferProhibited
Nameservers: dns1.namecheaphosting.com
dns2.namecheaphosting.com
Full Whois: Domain Name: MYCONTENTSTORE.COM
Registry Domain ID: 2503170799_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2020-03-13T21:54:31Z
Creation Date: 2020-03-13T21:54:24Z
Registry Expiry Date: 2021-03-13T21:54:24Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS1.NAMECHEAPHOSTING.COM
Name Server: DNS2.NAMECHEAPHOSTING.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2020-06-07T05:14:17Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

Nameservers

Name IP Address
dns1.namecheaphosting.com 156.154.132.200
dns2.namecheaphosting.com 156.154.133.200
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$761 USD 1/5
0/5
0/5
Love W3 Snoop?

mycontentstore.com Infographic

mycontentstore.com by the numbers infographic