mapleleaftimes.com

mapleleaftimes.com is SSL secured

Free website and domain report on mapleleaftimes.com

Last Updated: 1st October, 2024
Overview

Snoop Summary for mapleleaftimes.com

This is a free and comprehensive report about mapleleaftimes.com. The domain mapleleaftimes.com is currently hosted on a server located in Chicago, Illinois in United States with the IP address 104.130.210.203, where USD is the local currency and the local language is English. Our records indicate that mapleleaftimes.com is privately registered by Domains By Proxy, LLC. If mapleleaftimes.com was to be sold it would possibly be worth $713 USD (based on the daily revenue potential of the website over a 24 month period). Mapleleaftimes.com is somewhat popular with an estimated 338 daily unique visitors. This report was last updated 1st October, 2024.

About mapleleaftimes.com

Site Preview: mapleleaftimes.com mapleleaftimes.com
Title:
Description:
Keywords and Tags: business
Related Terms:
Fav Icon:
Age: Over 3 years old
Domain Created: 8th April, 2021
Domain Updated: 9th April, 2022
Domain Expires: 8th April, 2023
Review

Snoop Score

1/5

Valuation

$713 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,962,361
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 338
Monthly Visitors: 10,288
Yearly Visitors: 123,370
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $29 USD
Yearly Revenue: $352 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: mapleleaftimes.com 18
Domain Name: mapleleaftimes 14
Extension (TLD): com 3

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 69
Performance 78
Accessibility 73
Best Practices 92
SEO 82
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
78

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mapleleaftimes.com/
http/1.1
0
2098.7789999926
288
0
301
text/html
https://www.mapleleaftimes.com/
http/1.1
2099.1509999731
4433.2270000014
2039
4242
200
text/html
Document
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700&display=swap
h2
4445.7120000152
4458.2079999964
1503
8538
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
h2
4446.248000022
4458.7629999733
1419
4380
200
text/css
Stylesheet
https://www.mapleleaftimes.com/config.js
http/1.1
4446.4889999945
4761.1160000088
2106
1806
200
text/javascript
Script
https://www.mapleleaftimes.com/_nuxt/57dc5db.js
http/1.1
4446.763999993
4735.8050000039
1628
2590
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/3c74033.js
http/1.1
4446.9289999688
4778.8699999801
98450
295519
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
http/1.1
4447.3969999817
4702.0570000168
116366
442502
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/6542639.js
http/1.1
4447.7569999872
4770.1799999923
21294
206544
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
h2
4764.6400000085
4784.6370000043
46519
123053
200
application/javascript
Script
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
4924.7520000208
4928.2309999689
11972
11032
200
font/woff2
Font
https://www.mapleleaftimes.com/_nuxt/7c74603.js
http/1.1
4941.8319999822
5106.1909999698
6360
22159
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/717c323.js
http/1.1
4942.4959999742
5110.2659999742
7320
69933
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/898c662.js
http/1.1
4943.0270000012
5113.8219999848
12638
100952
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/2af6d72.js
http/1.1
4943.5560000129
5108.9420000208
7595
71393
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
h2
4960.0310000242
4973.7309999764
62976
168739
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
4963.7440000079
4968.3819999918
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1070979504&t=pageview&_s=1&dl=https%3A%2F%2Fwww.mapleleaftimes.com%2F&ul=en-us&de=UTF-8&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAEABAAAAAC~&jid=1378165529&gjid=354870258&cid=142171555.1641513965&tid=UA-241914-10&_gid=1871432632.1641513965&_r=1&gtm=2wg150KGCXW2X&cd1=mapleleaftimes.com&cd2=1&z=254011442
h2
4989.8790000007
4993.3109999984
620
1
200
text/plain
XHR
https://www.google-analytics.com/g/collect?v=2&tid=G-5VG3FMDW9W&gtm=2oe150&_p=1070979504&sr=800x600&ul=en-us&cid=142171555.1641513965&_s=1&dl=https%3A%2F%2Fwww.mapleleaftimes.com%2F&dt=&sid=1641513965&sct=1&seg=0&en=page_view&_fv=1&_ss=1
5033.3250000258
5036.4069999778
0
0
-1
Ping
https://www.mapleleaftimes.com/v1/token/mapleleaftimes/new
http/1.1
5165.3619999997
5344.5550000179
566
77
200
application/json
XHR
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/3407296-maple-leaf-times-logo-227x44c.svg
http/1.1
5401.8250000081
5956.3280000002
3632
10249
200
image/svg+xml
Image
https://www.mapleleaftimes.com/firebase-link-qr.svg
http/1.1
5402.2099999711
5659.8559999838
1154
2455
200
image/svg+xml
Image
https://www.tqlkg.com/image-100448887-14351705-1602888810000
http/1.1
5410.5689999997
5489.8410000023
503
0
302
text/html
https://www.mapleleaftimes.com/v1/press-releases/mapleleaftimes?offset=0
http/1.1
5411.9630000205
6901.7420000164
3401
14065
200
application/json
XHR
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
5416.9259999762
5420.5710000242
11988
11048
200
font/woff2
Font
https://www.mapleleaftimes.com/_nuxt/ffd38e5.js
http/1.1
5457.6140000136
5621.0340000107
2593
5403
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/e44dcf8.js
http/1.1
5458.0720000085
5621.5000000084
5782
46390
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/bd9ae89.js
http/1.1
5458.81500002
5756.1829999904
18687
72775
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/091c468.js
http/1.1
5459.2360000242
7675.6509999977
6666
46863
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/91eb69b.js
http/1.1
5459.9399999715
5575.0049999915
3724
21297
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/3758558.js
http/1.1
5460.6550000026
5620.1269999729
10893
47286
200
application/javascript
Script
https://www.yceml.net/0345/14351705-1602888810688
http/1.1
5490.0609999895
5659.4620000105
40953
40763
200
image/jpeg
Image
https://www.mapleleaftimes.com/v1/articles/mapleleaftimes?limit=17&offset=0
http/1.1
6907.5290000183
8097.9839999927
4914
13482
200
application/json
XHR
https://www.ftjcfx.com/image-100448887-12490428-1500390265000
8142.7479999838
0
0
-1
Image
data
8143.6359999934
8143.8080000225
0
42
200
image/gif
Image
https://www.ftjcfx.com/image-100448887-11478147-1623683972000
8177.6839999948
0
0
-1
Image
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/5231152-558992602-image-100x56.png
http/1.1
8205.5629999959
8427.2389999824
8404
8007
200
image/png
Image
https://www.mapleleaftimes.com/_nuxt/b8a1b1f.js
http/1.1
8214.4229999976
8419.9030000018
8083
81449
200
application/javascript
Script
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/5377018-559959131-web_SYRIAN_SOAP_CITIZEN_TUCKER_-100x56.jpeg
http/1.1
8341.0889999941
8999.8589999741
2772
2374
200
image/jpeg
Image
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/5376435-559956025-CITIZEN-100x53.jpeg
http/1.1
8341.745999991
8571.7740000109
3002
2604
200
image/jpeg
Image
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387321-depression-among-workers-900x564.jpeg
http/1.1
8342.4380000215
8450.3249999834
39072
38672
200
image/jpeg
Image
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387253-opie-s-crawfish-logo-800x800.jpeg
http/1.1
8343.0930000031
8448.5049999785
75754
75354
200
image/jpeg
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-5VG3FMDW9W&gtm=2oe150&_p=1070979504&sr=800x600&ul=en-us&cid=142171555.1641513965&_s=2&dl=https%3A%2F%2Fwww.mapleleaftimes.com%2F&dt=&sid=1641513965&sct=1&seg=0&en=scroll&_et=157&epn.percent_scrolled=90
10211.367000011
10219.049000007
0
0
-1
Ping
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)
4469.196
8.979
4800.319
7.447
4829.029
9.509
4839.12
140.112
4982.473
16.484
5007.743
16.663
5039.635
30.28
5152.662
6.239
5161.335
38.065
5215.202
26.91
5378.928
13.103
5392.725
53.428
5446.204
18.845
5468.153
6.873
5489.689
5.137
5661.377
5.821
6149.062
6.277
6323.201
5.235
6417.989
5.339
6427.721
9.431
6936.088
5.508
7114.068
7.11
7230.414
5.891
7247.136
10.032
7267.492
7.166
7299.39
9.561
7318.781
11.472
7711.28
11.184
8132.538
80.182
8212.832
23.947
8240.799
7.456
8456.241
7.877
8464.128
10.893
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images — Potential savings of 76 KiB
Images can slow down the page's load time. Mapleleaftimes.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387253-opie-s-crawfish-logo-800x800.jpeg
75354
53556
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387321-depression-among-workers-900x564.jpeg
38672
24567
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mapleleaftimes.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mapleleaftimes.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mapleleaftimes.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mapleleaftimes.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images — Potential savings of 5 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.yceml.net/0345/14351705-1602888810688
40763
5305
Serve images in next-gen formats — Potential savings of 79 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387253-opie-s-crawfish-logo-800x800.jpeg
75354
42218.4
https://www.yceml.net/0345/14351705-1602888810688
40763
22168.1
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387321-depression-among-workers-900x564.jpeg
38672
16335.3
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Mapleleaftimes.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mapleleaftimes.com/
190
https://www.mapleleaftimes.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mapleleaftimes.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 16 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.mapleleaftimes.com/_nuxt/3c74033.js
16076
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
504
https://www.mapleleaftimes.com/_nuxt/6542639.js
66
https://www.mapleleaftimes.com/_nuxt/091c468.js
23
https://www.mapleleaftimes.com/_nuxt/2af6d72.js
17
https://www.mapleleaftimes.com/_nuxt/b8a1b1f.js
16
https://www.mapleleaftimes.com/_nuxt/898c662.js
10
https://www.mapleleaftimes.com/_nuxt/e44dcf8.js
10
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 658 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
116366
https://www.mapleleaftimes.com/_nuxt/3c74033.js
98450
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387253-opie-s-crawfish-logo-800x800.jpeg
75754
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
62976
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
46519
https://www.yceml.net/0345/14351705-1602888810688
40953
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387321-depression-among-workers-900x564.jpeg
39072
https://www.mapleleaftimes.com/_nuxt/6542639.js
21294
https://www.google-analytics.com/analytics.js
20631
https://www.mapleleaftimes.com/_nuxt/bd9ae89.js
18687
Avoids an excessive DOM size — 442 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
442
Maximum DOM Depth
18
Maximum Child Elements
18
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mapleleaftimes.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.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.mapleleaftimes.com/
397.28
6.722
1.622
https://www.mapleleaftimes.com/_nuxt/898c662.js
190.326
165.612
2.04
https://www.mapleleaftimes.com/_nuxt/6542639.js
118.515
110.481
2.985
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
59.591
55.256
2.42
Unattributable
56.158
3.253
0.174
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)
Script Evaluation
434.058
Rendering
204.171
Other
143.932
Style & Layout
133.475
Script Parsing & Compilation
34.614
Parse HTML & CSS
11.545
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 — 42 requests • 658 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
42
674267
Script
19
460311
Image
10
174743
Font
2
23960
Other
8
10292
Stylesheet
2
2922
Document
1
2039
Media
0
0
Third-party
20
331720
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
132636
0
109495
0
26882
0
21251
0
503
0
0
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.092530167235794
0.0021683565362052
0.0019803519831889
0.0010893617021277
0.00062940898345154
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.mapleleaftimes.com/_nuxt/3c74033.js
1290
70
https://www.mapleleaftimes.com/_nuxt/898c662.js
1763
53
Avoid non-composited animations — 6 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
 
 
 
 
 
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 mapleleaftimes.com on mobile screens.

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.
Largest Contentful Paint — 2.0 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 300 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mapleleaftimes.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700&display=swap
1503
230
https://www.mapleleaftimes.com/config.js
2106
70
Reduce unused JavaScript — Potential savings of 156 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
116366
90808
https://www.mapleleaftimes.com/_nuxt/3c74033.js
98450
40307
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
62976
28320

Metrics

Speed Index — 4.5 s
The time taken for the page contents to be visibly populated.

Other

Reduce initial server response time — Root document took 2,340 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.mapleleaftimes.com/
2335.072
Serve static assets with an efficient cache policy — 24 resources found
Mapleleaftimes.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
0
116366
https://www.mapleleaftimes.com/_nuxt/3c74033.js
0
98450
https://www.mapleleaftimes.com/_nuxt/6542639.js
0
21294
https://www.mapleleaftimes.com/_nuxt/bd9ae89.js
0
18687
https://www.mapleleaftimes.com/_nuxt/898c662.js
0
12638
https://www.mapleleaftimes.com/_nuxt/3758558.js
0
10893
https://www.mapleleaftimes.com/_nuxt/b8a1b1f.js
0
8083
https://www.mapleleaftimes.com/_nuxt/2af6d72.js
0
7595
https://www.mapleleaftimes.com/_nuxt/717c323.js
0
7320
https://www.mapleleaftimes.com/_nuxt/091c468.js
0
6666
https://www.mapleleaftimes.com/_nuxt/7c74603.js
0
6360
https://www.mapleleaftimes.com/_nuxt/e44dcf8.js
0
5782
https://www.mapleleaftimes.com/_nuxt/91eb69b.js
0
3724
https://www.mapleleaftimes.com/_nuxt/ffd38e5.js
0
2593
https://www.mapleleaftimes.com/_nuxt/57dc5db.js
0
1628
https://www.mapleleaftimes.com/firebase-link-qr.svg
1800000
1154
https://www.google-analytics.com/analytics.js
7200000
20631
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/5231152-558992602-image-100x56.png
259144000
8404
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/5377018-559959131-web_SYRIAN_SOAP_CITIZEN_TUCKER_-100x56.jpeg
259188000
2772
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/5376435-559956025-CITIZEN-100x53.jpeg
259200000
3002
https://www.yceml.net/0345/14351705-1602888810688
565988000
40953
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/3407296-maple-leaf-times-logo-227x44c.svg
597820000
3632
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387321-depression-among-workers-900x564.jpeg
1205035000
39072
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/5387253-opie-s-crawfish-logo-800x800.jpeg
1205918000
75754
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.mapleleaftimes.com/firebase-link-qr.svg
https://www.mapleleaftimes.com/firebase-link-qr.svg
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/3407296-maple-leaf-times-logo-227x44c.svg
73

Accessibility

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

Navigation

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

ARIA

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

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

Names and labels

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

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"]`
Mapleleaftimes.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not 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.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

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

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Vue
Nuxt.js
core-js
core-js-global@3.18.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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

SEO

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

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

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

PWA

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

PWA Optimized

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

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 68
Performance 51
Accessibility 81
Best Practices 92
SEO 84
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
51

Performance

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

Metrics

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

Other

Properly size images
Images can slow down the page's load time. Mapleleaftimes.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mapleleaftimes.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mapleleaftimes.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mapleleaftimes.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mapleleaftimes.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
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 170 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.mapleleaftimes.com/
166.99
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Mapleleaftimes.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mapleleaftimes.com/
630
https://www.mapleleaftimes.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mapleleaftimes.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 16 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.mapleleaftimes.com/_nuxt/3c74033.js
16076
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
504
https://www.mapleleaftimes.com/_nuxt/6542639.js
66
https://www.mapleleaftimes.com/_nuxt/2af6d72.js
17
https://www.mapleleaftimes.com/_nuxt/898c662.js
10
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 651 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
116366
https://www.yceml.net/0394/14462346-1614360201845
113845
https://www.mapleleaftimes.com/_nuxt/3c74033.js
98450
https://www.yceml.net/0397/14462349-1614360201805
70420
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
62977
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
46519
https://www.mapleleaftimes.com/_nuxt/6542639.js
21294
https://www.google-analytics.com/analytics.js
20631
https://www.yceml.net/0474/10386906-1623696292351
13805
https://www.mapleleaftimes.com/_nuxt/898c662.js
12638
Avoids an excessive DOM size — 442 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
442
Maximum DOM Depth
18
Maximum Child Elements
18
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mapleleaftimes.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.
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 — 33 requests • 651 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
33
666309
Script
13
414779
Image
6
211260
Font
2
23959
Other
9
11304
Stylesheet
2
2968
Document
1
2039
Media
0
0
Third-party
17
369295
Minimize third-party usage — Third-party code blocked the main thread for 100 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)
109496
87.536
21251
16.568
26927
0
12036
0
506
0
506
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00013821125030518
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 8 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
5160
232
https://www.mapleleaftimes.com/_nuxt/2af6d72.js
6892
226
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
4432
124
https://www.mapleleaftimes.com/_nuxt/2af6d72.js
6540
116
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
7500
115
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
3150
82
https://www.google-analytics.com/analytics.js
4312
74
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
6836
56
Avoid non-composited animations — 6 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
 
 
 
 
 
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 mapleleaftimes.com on mobile screens.

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.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mapleleaftimes.com/
http/1.1
0
95.862000249326
288
0
301
text/html
https://www.mapleleaftimes.com/
http/1.1
96.23199980706
262.2260004282
2039
4242
200
text/html
Document
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700&display=swap
h2
272.89800066501
286.2590001896
1503
8538
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
h2
273.17200042307
285.46900022775
1465
5276
200
text/css
Stylesheet
https://www.mapleleaftimes.com/config.js
http/1.1
273.37700035423
476.66000016034
2108
1808
200
text/javascript
Script
https://www.mapleleaftimes.com/_nuxt/57dc5db.js
http/1.1
273.63499999046
460.73800045997
1628
2590
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/3c74033.js
http/1.1
273.8979998976
498.93399979919
98450
295519
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
http/1.1
274.1879997775
523.98400008678
116366
442502
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/6542639.js
http/1.1
274.40000046045
487.79400065541
21294
206544
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
h2
480.16600031406
497.84900061786
46519
123053
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
h2
544.60099991411
565.64700044692
62977
168739
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
550.11400021613
554.99100033194
20631
50205
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
651.18699986488
654.80200015008
11972
11032
200
font/woff2
Font
https://www.mapleleaftimes.com/_nuxt/7c74603.js
http/1.1
666.00000020117
830.39900008589
6360
22159
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/717c323.js
http/1.1
666.400000453
831.0170006007
7320
69933
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/898c662.js
http/1.1
666.97700042278
833.89599993825
12638
100952
200
application/javascript
Script
https://www.mapleleaftimes.com/_nuxt/2af6d72.js
http/1.1
667.3189997673
935.97299978137
7595
71393
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=890252485&t=pageview&_s=1&dl=https%3A%2F%2Fwww.mapleleaftimes.com%2F&ul=en-us&de=UTF-8&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAEABAAAAAC~&jid=1272324144&gjid=202512614&cid=960410198.1641513986&tid=UA-241914-10&_gid=1856715195.1641513986&_r=1&gtm=2wg150KGCXW2X&cd1=mapleleaftimes.com&cd2=1&z=1894518043
h2
693.79200041294
697.6960003376
620
1
200
text/plain
XHR
https://www.google-analytics.com/g/collect?v=2&tid=G-5VG3FMDW9W&gtm=2oe150&_p=890252485&sr=360x640&ul=en-us&cid=960410198.1641513986&_s=1&dl=https%3A%2F%2Fwww.mapleleaftimes.com%2F&dt=&sid=1641513986&sct=1&seg=0&en=page_view&_fv=1&_ss=1
723.36500044912
727.38699987531
0
0
-1
Ping
https://www.mapleleaftimes.com/v1/token/mapleleaftimes/new
http/1.1
967.1570006758
1143.214000389
566
77
200
application/json
XHR
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/3407296-maple-leaf-times-logo-227x44c.svg
http/1.1
1203.7519998848
1564.0350002795
3632
10249
200
image/svg+xml
Image
https://www.mapleleaftimes.com/firebase-link-qr.svg
http/1.1
1203.9799997583
1364.5370006561
1154
2455
200
image/svg+xml
Image
https://www.ftjcfx.com/image-100448887-14462349-1614360201000
http/1.1
1213.0009997636
1647.7749999613
506
0
302
text/html
https://www.mapleleaftimes.com/v1/press-releases/mapleleaftimes?offset=0
http/1.1
1214.4200000912
2344.5830000564
3401
14065
200
application/json
XHR
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1219.355000183
1222.6430000737
11987
11048
200
font/woff2
Font
https://www.mapleleaftimes.com/_nuxt/3758558.js
http/1.1
1255.7080006227
1367.4380006269
10893
47286
200
application/javascript
Script
https://www.yceml.net/0397/14462349-1614360201805
http/1.1
1648.1349999085
1781.2980003655
70420
70230
200
image/jpeg
Image
https://www.mapleleaftimes.com/v1/articles/mapleleaftimes?limit=17&offset=0
http/1.1
2350.4189997911
2545.7709999755
4914
13482
200
application/json
XHR
https://www.tqlkg.com/image-100448887-14462346-1614360201000
http/1.1
2574.5000001043
3011.5060005337
506
0
302
text/html
data
2574.4430003688
2574.576000683
0
42
200
image/gif
Image
https://www.awltovhc.com/image-100448887-10386906-1623696292000
http/1.1
2603.5080002621
2681.5470000729
503
0
302
text/html
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/5231152-558992602-image-100x56.png
http/1.1
2618.4740001336
2748.5090000555
8404
8007
200
image/png
Image
https://www.yceml.net/0474/10386906-1623696292351
http/1.1
2681.862000376
2802.5219999254
13805
13615
200
image/gif
Image
https://www.yceml.net/0394/14462346-1614360201845
http/1.1
3011.7450002581
3102.5189999491
113845
113654
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)
304.441
6.982
521.877
6.466
551.009
9.284
560.837
9.697
571.864
20.416
592.988
115.756
715.801
18.561
735.22
30.875
978.372
29.027
1183.743
13.883
1198.298
56.43
1254.781
15.653
1410.152
5.572
2385.128
5.521
2586.35
57.712
2644.151
13.202
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Time to Interactive — 6.9 s
The time taken for the page to become fully interactive.
Speed Index — 5.1 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 460 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).

Audits

Max Potential First Input Delay — 230 ms
Users could experience a delay when interacting with the page.

Other

Efficiently encode images — Potential savings of 129 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.yceml.net/0394/14462346-1614360201845
113654
82319
https://www.yceml.net/0397/14462349-1614360201805
70230
49280
Serve images in next-gen formats — Potential savings of 155 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.yceml.net/0394/14462346-1614360201845
113654
98258.65
https://www.yceml.net/0397/14462349-1614360201805
70230
60766.1
Reduce JavaScript execution time — 1.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.mapleleaftimes.com/
701.96
25.052
5.596
https://www.mapleleaftimes.com/_nuxt/2af6d72.js
647.824
582.284
5.876
https://www.mapleleaftimes.com/_nuxt/6542639.js
404.18
369.52
12.776
Unattributable
170.052
10.788
0.508
https://www.googletagmanager.com/gtm.js?id=GTM-KGCXW2X
153.624
138.94
8.824
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
127.204
112.648
10.536
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
81.356
18.736
27.224
https://www.google-analytics.com/analytics.js
77.82
69.324
3.892
https://www.mapleleaftimes.com/_nuxt/3c74033.js
61.404
6.452
18.752
Minimize main-thread work — 2.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1354.072
Other
403.884
Style & Layout
313.312
Rendering
275.088
Script Parsing & Compilation
109.668
Parse HTML & CSS
22.272

Metrics

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

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 1,460 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mapleleaftimes.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700&display=swap
1503
780
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
1465
150
https://www.mapleleaftimes.com/config.js
2108
180
Reduce unused JavaScript — Potential savings of 156 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
116366
90906
https://www.mapleleaftimes.com/_nuxt/3c74033.js
98450
40307
https://www.googletagmanager.com/gtag/js?id=G-5VG3FMDW9W&l=dataLayer&cx=c
62977
28469
Serve static assets with an efficient cache policy — 16 resources found
Mapleleaftimes.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.mapleleaftimes.com/_nuxt/75f8b58.js
0
116366
https://www.mapleleaftimes.com/_nuxt/3c74033.js
0
98450
https://www.mapleleaftimes.com/_nuxt/6542639.js
0
21294
https://www.mapleleaftimes.com/_nuxt/898c662.js
0
12638
https://www.mapleleaftimes.com/_nuxt/3758558.js
0
10893
https://www.mapleleaftimes.com/_nuxt/2af6d72.js
0
7595
https://www.mapleleaftimes.com/_nuxt/717c323.js
0
7320
https://www.mapleleaftimes.com/_nuxt/7c74603.js
0
6360
https://www.mapleleaftimes.com/_nuxt/57dc5db.js
0
1628
https://www.mapleleaftimes.com/firebase-link-qr.svg
1800000
1154
https://www.google-analytics.com/analytics.js
7200000
20631
https://www.yceml.net/0397/14462349-1614360201805
135272000
70420
https://2c717466dc25cd7041c9-8eeda6a8ca964cf210ed223dbc947813.ssl.cf2.rackcdn.com/5231152-558992602-image-100x56.png
259124000
8404
https://www.yceml.net/0394/14462346-1614360201845
339237000
113845
https://www.yceml.net/0474/10386906-1623696292351
432321000
13805
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/3407296-maple-leaf-times-logo-227x44c.svg
597800000
3632
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://d2c0db5b8fb27c1c9887-9b32efc83a6b298bb22e7a1df0837426.ssl.cf2.rackcdn.com/3407296-maple-leaf-times-logo-227x44c.svg
First Contentful Paint (3G) — 9082 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
81

Accessibility

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

Navigation

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

ARIA

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

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

Names and labels

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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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"]`
Mapleleaftimes.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not 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.
Failing Elements

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

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Vue
Nuxt.js
core-js
core-js-global@3.18.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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mapleleaftimes.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 mapleleaftimes.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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 — 96% 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
103x16

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

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

PWA

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

PWA Optimized

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

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 104.130.210.203
Continent: North America
Country: United States
United States Flag
Region: Illinois
City: Chicago
Longitude: -87.6563
Latitude: 41.9017
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Rackspace Hosting
Registration

Domain Registrant

Private Registration: Yes
Name: Registration Private
Organization: Domains By Proxy, LLC
Country: US
City: Tempe
State: Arizona
Post Code: 85284
Email:
Phone: +1.4806242599
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.204.211.225
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: www.africanewsobserver.com
Issued By: R10
Valid From: 30th August, 2024
Valid To: 28th November, 2024
Subject: CN = www.africanewsobserver.com
Hash: 60ff0852
Issuer: CN = R10
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03E2BA541D2857B1C14675BA7E29585AE73E
Serial Number (Hex): 03E2BA541D2857B1C14675BA7E29585AE73E
Valid From: 30th August, 2024
Valid To: 28th November, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://r10.o.lencr.org
CA Issuers - URI:http://r10.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Aug 30 17:19:10.729 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:5E:80:36:FC:6A:3D:6C:16:0A:C9:77:D0:
3C:DE:64:84:61:86:D2:D7:30:FB:1D:1F:2C:40:8C:F4:
8A:1F:DD:F7:02:21:00:AF:F9:3B:6F:D6:13:28:A6:4E:
7F:4C:B9:B8:CB:0B:7A:39:44:2C:85:BD:5D:D5:65:08:
29:DB:58:7A:90:FB:70
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
Timestamp : Aug 30 17:19:10.802 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:1C:12:61:C8:CD:8B:04:CA:15:32:35:53:
16:5C:1B:F0:02:44:77:18:A4:92:E1:0F:A8:8D:BD:C2:
21:F6:BC:6F:02:20:19:A4:98:64:A4:00:44:CE:01:25:
15:05:EE:D3:72:19:C9:5C:60:25:F0:3B:4D:C9:C5:A4:
77:EC:05:67:DE:B7
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.africapoliticaljournal.com
DNS:www.americalatinatimes.com
DNS:www.americanpublishertoday.com
DNS:www.asiahealthcareindustrydigest.com
DNS:www.asiapacifictransportationtimes.com
DNS:www.australiannewsexpress.com
DNS:www.australiannewsjournal.com
DNS:www.businesstimesjournal.com
DNS:www.canadaeducationnewswire.com
DNS:www.canadianagriculturetimes.com
DNS:www.canadianenvironmentalnewswire.com
DNS:www.cannabidiolhealthcarenews.com
DNS:www.cryptoinsiderreview.com
DNS:www.deutschlanddailynews.com
DNS:www.deutschlandtimes.com
DNS:www.downunderbookworld.com
DNS:www.economicnewsobserver.com
DNS:www.europeanledger.com
DNS:www.florida-gazette.com
DNS:www.florida-observer.com
DNS:www.floridamanufacturingtimes.com
DNS:www.floridamusicbeat.com
DNS:www.floridanewsguide.com
DNS:www.floridapoliticaljournal.com
DNS:www.floridasmallbusinesstoday.com
DNS:www.germanculturereport.com
DNS:www.globalculturereview.com
DNS:www.globalhealthcaretoday.com
DNS:www.globallogisticsupdate.com
DNS:www.globalngoreview.com
DNS:www.globaltravelnetworknews.com
DNS:www.healthylivingeurope.com
DNS:www.humanresourcestimes.com
DNS:www.italianmusician.com
DNS:www.italyrealestatenews.com
DNS:www.journalofbusinessnews.com
DNS:www.journalofprofessionaltransportation.com
DNS:www.latinamericaenergyindustryjournal.com
DNS:www.latinamericahealthtimes.com
DNS:www.manufacturingeurope.com
DNS:www.mapleleaftimes.com
DNS:www.mediaworldtoday.com
DNS:www.middleeastagriculturereview.com
DNS:www.middleeastenvironmentalnews.com
DNS:www.middleeastnewswatch.com
DNS:www.middleeasttechtoday.com
DNS:www.musicindustrywatch.com
DNS:www.needtoknowcbd.com
DNS:www.non-profitsinthenews.com
DNS:www.northamericatoday.com
DNS:www.smallbusinesstimesofcanada.com
DNS:www.stemnewstoday.com
DNS:www.streamingmusictimes.com
DNS:www.technologynewsjournal.com
DNS:www.theamericanmusicreporter.com
DNS:www.theamericawatch.com
DNS:www.thefloridanewsguide.com
DNS:www.thegermanbusinessreport.com
DNS:www.theworldnewswire.com
DNS:www.todayfromcanada.com
DNS:www.transportationprofessionaltimes.com
DNS:www.transportationtimesofspain.com
DNS:www.travelindustrytimes.com
DNS:www.ukhealthcaregazette.com
DNS:www.ukpostobserver.com
DNS:www.usmanufacturingreporter.com
DNS:www.ustimesgazette.com
DNS:www.viaggioitaly.com
DNS:www.worldgovernmentswatch.com
DNS:www.worldhealthcarereport.com
DNS:www.worldonlinenewsreports.com
DNS:www.africanewsobserver.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
mapleleaftimes.com. 104.130.210.203 IN 10800

NS Records

Host Nameserver Class TTL
mapleleaftimes.com. ns5.newsmatics.com. IN 10800
mapleleaftimes.com. ns.newsmatics.com. IN 10800
mapleleaftimes.com. ns3.newsmatics.com. IN 10800
mapleleaftimes.com. ans.newsmatics.com. IN 10800

MX Records

Priority Host Server Class TTL
10 mapleleaftimes.com. mail6.cloud.ipdgroup.com. IN 10800
10 mapleleaftimes.com. mail2.cloud.ipdgroup.com. IN 10800
10 mapleleaftimes.com. mail1.cloud.ipdgroup.com. IN 10800

SOA Records

Domain Name Primary NS Responsible Email TTL
mapleleaftimes.com. ns.newsmatics.com. hostmaster.ein.cz. 10800

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 1st October, 2024
Content-Type: text/html
Content-Length: 4240
Last-Modified: 2nd September, 2024
Connection: keep-alive
Keep-Alive: timeout=10
Vary: Accept-Encoding
ETag: "66d58cb1-1090"
Accept-Ranges: bytes

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ans.newsmatics.com
ns.newsmatics.com
ns3.newsmatics.com
ns5.newsmatics.com
Full Whois: Rate limit exceeded. Try again after: 24h0m0s

Nameservers

Name IP Address
ans.newsmatics.com 3.21.185.186
ns.newsmatics.com 173.203.107.116
ns3.newsmatics.com 104.130.207.141
ns5.newsmatics.com 23.253.164.79
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
0/5
0/5
0/5
$108 USD 1/5
$310 USD 1/5