lindsaysilberman.com

lindsaysilberman.com is SSL secured

Free website and domain report on lindsaysilberman.com

Last Updated: 10th January, 2022 Update Now
Overview

Snoop Summary for lindsaysilberman.com

This is a free and comprehensive report about lindsaysilberman.com. The domain lindsaysilberman.com is currently hosted on a server located in United States with the IP address 172.67.140.219, where the local currency is USD and English is the local language. Lindsaysilberman.com has the potential to be earning an estimated $6 USD per day from advertising revenue. If lindsaysilberman.com was to be sold it would possibly be worth $4,258 USD (based on the daily revenue potential of the website over a 24 month period). Lindsaysilberman.com receives an estimated 2,042 unique visitors every day - a large amount of traffic! This report was last updated 10th January, 2022.

About lindsaysilberman.com

Site Preview: lindsaysilberman.com lindsaysilberman.com
Title: Lindsay Silberman | NYC Lifestyle Blogger
Description: Lindsay Silberman is a New York City lifestyle blogger and influencer who specializes in luxury travel, beauty, and fashion.
Keywords and Tags: blogs, wiki
Related Terms: 2performant influencer, influencer, lifestyle blogger, lindsay, lindsay buroker, lindsay lohan mugshot, norman lindsay, phillip lindsay
Fav Icon:
Age: Over 8 years old
Domain Created: 22nd March, 2016
Domain Updated: 7th March, 2021
Domain Expires: 22nd March, 2022
Review

Snoop Score

2/5

Valuation

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

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 300,840
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: 2,042
Monthly Visitors: 62,152
Yearly Visitors: 745,330
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $6 USD
Monthly Revenue: $177 USD
Yearly Revenue: $2,124 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: lindsaysilberman.com 20
Domain Name: lindsaysilberman 16
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 71
Performance 67
Accessibility 80
Best Practices 77
SEO 100
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.lindsaysilberman.com/
Updated: 10th January, 2022
Simulate loading on desktop
67

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.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).

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
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://lindsaysilberman.com/
http/1.1
0
147.40999997593
868
0
301
text/html
https://lindsaysilberman.com/
http/1.1
147.70700014196
370.83399994299
1064
0
301
text/html
https://www.lindsaysilberman.com/
h2
371.21000001207
730.21599999629
25192
136929
200
text/html
Document
https://fonts.googleapis.com/css?family=Roboto:300&display=swap
h2
740.7850001473
756.53299991973
1331
2204
200
text/css
Stylesheet
https://www.lindsaysilberman.com/wp-content/cache/min/1/95c8d3aa2b915d26a3cbec15bb7e2d76.css
h2
741.20600009337
872.75100010447
96832
492906
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-90939214-1
h2
753.07799992152
786.40000009909
37109
92509
200
application/javascript
Script
https://www.lindsaysilberman.com/wp-content/plugins/social-pug/assets/dist/style-frontend-pro.1.19.1.css
h2
741.67999997735
800.60700001195
10637
101626
200
text/css
Stylesheet
https://scripts.mediavine.com/tags/lindsay-silberman.js
h2
753.19800013676
769.49999993667
19044
66102
200
application/javascript
Script
https://www.lindsaysilberman.com/wp-includes/js/jquery/jquery.min.js
h2
753.32100014202
805.33000011928
32958
89496
200
application/javascript
Script
https://www.lindsaysilberman.com/wp-content/themes/sitka/fonts/fontawesome-webfont.woff2?v=4.7.0
h2
742.17300000601
818.39099992067
78151
77160
200
font/woff2
Font
https://www.lindsaysilberman.com/wp-content/fonts/montserrat/JTUSjIg1_i6t8kCHKm459WlhzSTh89Y.woff
h2
742.37400013953
856.06299992651
18868
17888
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/lora/0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mvWc3ZyhTg.woff
h2
742.72500001825
811.59800011665
26537
25544
200
font/woff
Font
https://www.lindsaysilberman.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
h2
749.62699995376
801.19500006549
1480
1239
200
application/javascript
Script
https://z-na.associates-amazon.com/onetag/v2?MarketPlace=US&instanceId=124519c3-f4ec-438a-9ec7-329cf1133209
h2
753.68200009689
769.86499992199
499
23
200
text/javascript
Script
data
757.19500007108
757.26000010036
0
64
200
image/svg+xml
Image
data
758.13700002618
758.18999996409
0
69
200
image/svg+xml
Image
data
758.9910000097
759.05300001614
0
68
200
image/svg+xml
Image
data
760.00800007023
760.07500011474
0
66
200
image/svg+xml
Image
data
760.89400006458
760.9480000101
0
68
200
image/svg+xml
Image
https://www.lindsaysilberman.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
h2
762.33600010164
788.41600008309
3692
7890
200
application/javascript
Script
https://www.lindsaysilberman.com/wp-content/cache/min/1/46e14bcef8579ee91e2e19346a347573.js
h2
762.67800014466
844.17900000699
25334
86267
200
application/javascript
Script
https://scripts.mediavine.com/tags/2.73.1/wrapper.min.js?bust=-2020171008
h2
781.42499993555
798.42699994333
46417
146239
200
application/javascript
Script
https://exchange.mediavine.com/usersync.min.js?s2sVersion=ADT-341-Native2BidTellect-c
h2
781.70199994929
839.96000001207
4682
14012
200
application/javascript
Script
https://keywords.mediavine.com/keyword/web.keywords.js?pageUrl=https://www.lindsaysilberman.com/
h2
782.15500013903
822.09399994463
716
384
200
text/html
Script
https://www.lindsaysilberman.com/wp-content/fonts/karla/qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lMZbLXGimS.woff
h2
801.10800010152
830.52999991924
15895
14904
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/montserrat/JTURjIg1_i6t8kCHKm45_dJE3gnD-Px3rCs.woff
h2
801.46800004877
824.99000011012
18069
17076
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/playfair-display/nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtXK-F2qO0g.woff
h2
801.67700001039
827.48800003901
25049
24064
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/karla/qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlCV3lIb7X1HgGQ0tQ.woff
h2
804.29000011645
827.94600003399
16131
15152
200
font/woff
Font
https://www.google-analytics.com/analytics.js
h2
862.29500011541
867.41800000891
20631
50205
200
text/javascript
Script
https://www.lindsaysilberman.com/wp-content/fonts/poppins/pxiEyp8kv8JHgFVrJJfedHFHGPc.woff
h2
868.17099992186
901.1129999999
11519
10536
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/LS-Main-Logo_teal-1.png
h2
912.14699996635
934.7500000149
4958
3972
200
image/webp
Image
https://www.lindsaysilberman.com/wp-content/uploads/2020/07/lindsay-silberman-amazon.jpg
h2
912.31600008905
934.33100008406
14694
13700
200
image/webp
Image
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/lindsay_silberman_travel_guide-3.jpg
h2
912.44600014761
940.30599994585
140665
139680
200
image/webp
Image
https://www.lindsaysilberman.com/wp-content/uploads/2020/07/Lindsay-Silberman-Beauty-Tips.jpg
h2
912.68500010483
935.0310000591
13828
12840
200
image/jpeg
Image
https://www.lindsaysilberman.com/wp-content/uploads/2021/07/best-amazon-finds-1140x760.jpg
h2
914.52599992044
951.03899994865
156662
155672
200
image/jpeg
Image
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/lindsay_silberman_headshot-2.jpg
h2
914.62499997579
939.57799999043
53449
52465
200
image/jpeg
Image
https://assets.flodesk.com/universal.js?v=1641849959829
http/1.1
917.91500011459
1083.7930000853
21715
58927
200
application/javascript
Script
https://assets.flodesk.com/universal.mjs?v=820924920
http/1.1
918.97400002927
1046.8310001306
17697
46164
200
application/javascript
Script
https://assets.pinterest.com/js/pinit_main.js
h2
946.30499999039
973.93400012515
19065
68091
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1442589642&t=pageview&_s=1&dl=https%3A%2F%2Fwww.lindsaysilberman.com%2F&ul=en-us&de=UTF-8&dt=Lindsay%20Silberman%20%7C%20NYC%20Lifestyle%20Blogger&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=366605096&gjid=1690828617&cid=1614143145.1641849960&tid=UA-90939214-1&_gid=1352704256.1641849960&_r=1&gtm=2ou150&did=dNDMyYj&gdid=dNDMyYj&z=1635086814
h2
1018.3270000853
1022.2080000676
623
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j96&tid=UA-90939214-1&cid=1614143145.1641849960&jid=366605096&gjid=1690828617&_gid=1352704256.1641849960&_u=YEBAAUAAAAAAAC~&z=69147114
h2
1072.6749999449
1080.820000032
695
1
200
text/plain
XHR
https://www.lindsaysilberman.com/wp-content/plugins/forget-about-shortcode-buttons/public/fonts/fontawesome-webfont.woff?v=4.0.3
h2
1179.6939999331
1297.0859999768
45425
44432
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/karla/qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aE0lMZbLXGimS.woff
h2
1179.802000057
1378.2140000258
16008
15016
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/uploads/2021/12/best-things-to-do-in-palm-beach-1-1140x760.jpg
h2
1221.1939999834
1369.1180001479
138030
137045
200
image/jpeg
Image
https://www.lindsaysilberman.com/wp-content/uploads/2020/05/best_wines_under_30-1140x729.jpg
h2
1221.5800001286
1474.94500014
31992
31018
200
image/webp
Image
https://form.flodesk.com/forms/61a822bb6fd16bd0a4ddb27a
h2
1240.8880000003
1388.4870000184
5230
31932
200
text/html
XHR
https://form.flodesk.com/forms/5f189543626753002668ff39
h2
1243.2500000577
1379.1460001376
419
57
404
application/json
XHR
https://assets.flodesk.com/168.2fa5ebf16447e1819808.mjs
http/1.1
1384.9740000442
1474.3180000223
10650
31126
200
application/javascript
Script
https://assets.flodesk.com/54.92d0452c975a3bf2796b.mjs
http/1.1
1385.0920000114
1475.7840000093
6362
17515
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Montserrat:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i&display=swap
h2
1398.5649999231
1491.6300000623
2001
31778
200
text/css
Stylesheet
https://assets.flodesk.com/650.cffd7fef2e6357cc73d2.mjs
http/1.1
1401.8989999313
1565.7309999224
8242
20865
200
application/javascript
Script
https://usercontent.flodesk.com/ec4deb1f-4627-4707-8c63-45f221cd140a/upload/04032cbc-dfa3-4972-9605-2e74550a0032.jpeg
http/1.1
1415.2560001239
1549.9950000085
382452
381953
200
image/jpeg
Image
https://www.lindsaysilberman.com/wp-content/fonts/karla/qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lMZbLXGimS.woff
h2
1415.3670000378
1440.8750000875
15885
14900
200
font/woff
Font
https://usercontent.flodesk.com/forms/5f189543626753002668ff39/data.json?v=820924980
http/1.1
1591.7370000388
1722.2710000351
4353
15761
200
application/json
XHR
https://usercontent.flodesk.com/forms/5f189543626753002668ff39/data.json?v=820924980
http/1.1
1491.478000069
1591.2490000483
621
0
200
Preflight
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_dJE3gnD_vx3rCs.woff2
h2
1515.4069999699
1523.349000141
15056
14116
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
h2
1523.9409999922
1528.6099999212
15112
14172
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_cJD3gnD_vx3rCs.woff2
h2
1524.5749999303
1528.9370000828
15040
14100
200
font/woff2
Font
https://fonts.googleapis.com/css?family=Montserrat:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i&display=swap
h2
1755.7389999274
1756.0290000401
2001
31778
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Raleway:300,300i,400,400i,700,700i
h2
1756.7770001478
1777.1400001366
1475
9531
200
text/css
Stylesheet
https://assets.flodesk.com/form.js?v=1641849960637
http/1.1
1758.6860000156
1822.1269999631
28626
84144
200
application/javascript
Script
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_cJD3gnD_vx3rCs.woff2
h2
1765.4290001374
1765.6360000838
15040
14100
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
h2
1766.1079999525
1766.2210001145
15112
14172
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_dJE3gnD_vx3rCs.woff2
h2
1767.3879999202
1767.509000143
15056
14116
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
h2
1770.6170000602
1774.5000000577
15092
14152
200
font/woff2
Font
https://log.pinterest.com/?type=pidget&guid=9eXpL6Hke9rB&tv=2021110201&event=init&sub=www&button_count=0&follow_count=0&pin_count=0&profile_count=0&board_count=0&section_count=0&xload=1&lang=en&nvl=en-US&via=https%3A%2F%2Fwww.lindsaysilberman.com%2F&viaSrc=canonical
h2
2216.5020001121
2237.4170001131
534
0
200
text/plain
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)
775.187
6.732
793.144
10.631
816.274
8.162
834.8
25.442
863.16
8.587
872.745
5.271
880.005
11.125
896.572
7.943
908.475
12.278
922.11
27.98
955.791
17.577
975.177
7.638
988.684
48.093
1039.484
21.624
1062.445
6.246
1073.84
25.655
1099.638
12.66
1114.724
53.401
1169.154
16.537
1187.906
64.555
1252.54
7.588
1266.132
6.527
1272.672
10.53
1283.229
13.141
1296.627
60.36
1376.85
25.205
1436.938
6.255
1443.227
27.586
1499.991
19.26
1524.329
8.189
1541.938
27.487
1588.523
15.491
1613.353
14.781
1628.332
30.883
1659.418
7.042
1667.854
10.444
1694.653
13.391
1765.33
37.326
1802.762
18.595
1825.943
10.811
1872.352
18.498
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

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lindsaysilberman.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 127 KiB
Images can slow down the page's load time. Lindsaysilberman.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lindsaysilberman.com/wp-content/uploads/2021/07/best-amazon-finds-1140x760.jpg
155672
82795
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/lindsay_silberman_headshot-2.jpg
52465
47341
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Lindsaysilberman.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lindsaysilberman.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lindsaysilberman.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 102 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lindsaysilberman.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://www.lindsaysilberman.com/wp-content/cache/min/1/95c8d3aa2b915d26a3cbec15bb7e2d76.css
96832
92493
span.PIN_1641849960124_embed_grid { width: 100%; max-width: 257px; min-width: 140px; ... } ...
12244
12244
Reduce unused JavaScript — Potential savings of 26 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://scripts.mediavine.com/tags/2.73.1/wrapper.min.js?bust=-2020171008
46417
26477
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 360 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.lindsaysilberman.com/
359.999
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lindsaysilberman.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 26 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://assets.flodesk.com/form.js?v=1641849960637
13904
https://assets.flodesk.com/universal.js?v=1641849959829
12500
https://www.lindsaysilberman.com/
167
https://www.lindsaysilberman.com/wp-content/cache/min/1/46e14bcef8579ee91e2e19346a347573.js
49
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 1,747 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://usercontent.flodesk.com/ec4deb1f-4627-4707-8c63-45f221cd140a/upload/04032cbc-dfa3-4972-9605-2e74550a0032.jpeg
382452
https://www.lindsaysilberman.com/wp-content/uploads/2021/07/best-amazon-finds-1140x760.jpg
156662
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/lindsay_silberman_travel_guide-3.jpg
140665
https://www.lindsaysilberman.com/wp-content/uploads/2021/12/best-things-to-do-in-palm-beach-1-1140x760.jpg
138030
https://www.lindsaysilberman.com/wp-content/cache/min/1/95c8d3aa2b915d26a3cbec15bb7e2d76.css
96832
https://www.lindsaysilberman.com/wp-content/themes/sitka/fonts/fontawesome-webfont.woff2?v=4.7.0
78151
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/lindsay_silberman_headshot-2.jpg
53449
https://scripts.mediavine.com/tags/2.73.1/wrapper.min.js?bust=-2020171008
46417
https://www.lindsaysilberman.com/wp-content/plugins/forget-about-shortcode-buttons/public/fonts/fontawesome-webfont.woff?v=4.0.3
45425
https://www.googletagmanager.com/gtag/js?id=UA-90939214-1
37109
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Lindsaysilberman.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.lindsaysilberman.com/
452.605
11.524
2.236
https://assets.flodesk.com/54.92d0452c975a3bf2796b.mjs
152.178
63.525
1.273
Unattributable
99.156
2.84
0.136
https://www.lindsaysilberman.com/wp-content/cache/min/1/46e14bcef8579ee91e2e19346a347573.js
72.022
42.267
1.289
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
291.535
Style & Layout
265.844
Other
229.475
Rendering
163.606
Parse HTML & CSS
37.546
Script Parsing & Compilation
17.449
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 — 61 requests • 1,747 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
61
1788570
Image
10
937264
Font
18
393045
Script
18
304919
Stylesheet
6
114277
Document
1
25192
Other
8
13873
Media
0
0
Third-party
33
748698
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)
112316
0
70859
0
37109
0
21254
0
19599
0
695
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.47919977660524
0.41726833894737
0.13322655010067
0.064936215674311
0.059397411912247
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
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 lindsaysilberman.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

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

Other

Serve images in next-gen formats — Potential savings of 230 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://usercontent.flodesk.com/ec4deb1f-4627-4707-8c63-45f221cd140a/upload/04032cbc-dfa3-4972-9605-2e74550a0032.jpeg
381953
123200.6
https://www.lindsaysilberman.com/wp-content/uploads/2021/07/best-amazon-finds-1140x760.jpg
155672
56681.4
https://www.lindsaysilberman.com/wp-content/uploads/2021/12/best-things-to-do-in-palm-beach-1-1140x760.jpg
137045
55786.95
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Lindsaysilberman.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lindsaysilberman.com/
190
https://lindsaysilberman.com/
150
https://www.lindsaysilberman.com/
0
Serve static assets with an efficient cache policy — 4 resources found
Lindsaysilberman.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://z-na.associates-amazon.com/onetag/v2?MarketPlace=US&instanceId=124519c3-f4ec-438a-9ec7-329cf1133209
0
499
https://assets.pinterest.com/js/pinit_main.js
285000
19065
https://www.google-analytics.com/analytics.js
7200000
20631
https://www.lindsaysilberman.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000
1480
Avoid an excessive DOM size — 859 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
859
Maximum DOM Depth
15
Maximum Child Elements
28

Metrics

Largest Contentful Paint — 2.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 1.238
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Avoid `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.
Source
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.lindsaysilberman.com/wp-content/uploads/2020/08/lindsay_silberman_headshot-2.jpg
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/LS-Main-Logo_teal-1.png
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/LS-Main-Logo_teal-1.png
80

Accessibility

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

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.
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"]`
Lindsaysilberman.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
`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.

Contrast

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

Navigation

`[id]` attributes on active, focusable elements are not 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.
Failing Elements
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

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 lindsaysilberman.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.
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
jQuery
3.5.1
WordPress
5.8.3
core-js
core-js-global@3.16.0; core-js-global@3.16.0; core-js-pure@3.15.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://scripts.mediavine.com/tags/lindsay-silberman.js
https://scripts.mediavine.com/tags/launcher.min.js.map;
https://scripts.mediavine.com/tags/2.73.1/wrapper.min.js?bust=-2020171008
https://scripts.mediavine.com/tags/2.73.1/wrapper.min.js.map
https://exchange.mediavine.com/usersync.min.js?s2sVersion=ADT-341-Native2BidTellect-c
https://exchange.mediavine.com/usersync.min.js.map
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://lindsaysilberman.com/
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
200 x 150 (1.33)
300 x 150 (2.00)

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for lindsaysilberman.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 lindsaysilberman.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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the 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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

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

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 lindsaysilberman.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 lindsaysilberman.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

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
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) 63
Performance 27
Accessibility 80
Best Practices 77
SEO 100
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.lindsaysilberman.com/
Updated: 10th January, 2022
Simulate loading on mobile
27

Performance

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

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lindsaysilberman.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Lindsaysilberman.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Lindsaysilberman.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lindsaysilberman.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lindsaysilberman.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 130 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.lindsaysilberman.com/
126.266
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lindsaysilberman.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 1,538 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://usercontent.flodesk.com/ec4deb1f-4627-4707-8c63-45f221cd140a/upload/04032cbc-dfa3-4972-9605-2e74550a0032.jpeg
382452
https://www.lindsaysilberman.com/wp-content/uploads/2021/07/best-amazon-finds-1140x760.jpg
156662
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/lindsay_silberman_travel_guide-3.jpg
140666
https://www.lindsaysilberman.com/wp-content/cache/min/1/95c8d3aa2b915d26a3cbec15bb7e2d76.css
96840
https://www.lindsaysilberman.com/wp-content/themes/sitka/fonts/fontawesome-webfont.woff2?v=4.7.0
78151
https://scripts.mediavine.com/tags/2.73.1-fixBidderSyncs/wrapper.min.js?bust=169709059
46431
https://www.lindsaysilberman.com/wp-content/plugins/forget-about-shortcode-buttons/public/fonts/fontawesome-webfont.woff?v=4.0.3
45421
https://www.googletagmanager.com/gtag/js?id=UA-90939214-1
37109
https://www.lindsaysilberman.com/wp-includes/js/jquery/jquery.min.js
32938
https://assets.flodesk.com/form.js?v=1641849980933
28626
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Lindsaysilberman.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 — 59 requests • 1,538 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
59
1574664
Image
7
719241
Font
18
392987
Script
19
309072
Stylesheet
6
114323
Document
1
25172
Other
8
13869
Media
0
0
Third-party
34
752881
Minimize third-party usage — Third-party code blocked the main thread for 140 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)
21254
65.516
70864
62.32
37109
8.608
112349
0
19599
0
695
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 — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.48190382650535
0.10358848916658
0.060210809328075
Avoid long main-thread tasks — 15 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.lindsaysilberman.com/wp-includes/js/jquery/jquery.min.js
10181
212
https://scripts.mediavine.com/tags/2.73.1-fixBidderSyncs/wrapper.min.js?bust=169709059
4839
196
https://www.lindsaysilberman.com/
2324
159
https://www.lindsaysilberman.com/wp-includes/js/jquery/jquery.min.js
10393
133
https://assets.flodesk.com/form.js?v=1641849980933
13626
111
https://www.lindsaysilberman.com/
2150
97
https://assets.flodesk.com/universal.js?v=1641849980050
11410
96
https://www.lindsaysilberman.com/
5035
86
https://assets.flodesk.com/54.4749e9826da05043f33e.js
13062
84
https://www.lindsaysilberman.com/wp-includes/js/jquery/jquery.min.js
8940
78
https://scripts.mediavine.com/tags/lindsay-silberman.js
3420
69
https://www.lindsaysilberman.com/
2522
66
https://www.google-analytics.com/analytics.js
5201
65
https://www.googletagmanager.com/gtag/js?id=UA-90939214-1
3911
60
https://www.googletagmanager.com/gtag/js?id=UA-90939214-1
10547
56
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 lindsaysilberman.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://lindsaysilberman.com/
http/1.1
0
99.878000095487
863
0
301
text/html
https://lindsaysilberman.com/
http/1.1
100.37800017744
340.78299999237
1058
0
301
text/html
https://www.lindsaysilberman.com/
h2
341.22400009073
466.49700007401
25172
136929
200
text/html
Document
https://fonts.googleapis.com/css?family=Roboto:300&display=swap
h2
482.49900015071
503.00700007938
1364
2715
200
text/css
Stylesheet
https://www.lindsaysilberman.com/wp-content/cache/min/1/95c8d3aa2b915d26a3cbec15bb7e2d76.css
h2
483.00300003029
555.88100012392
96840
492906
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-90939214-1
h2
502.8300001286
525.5120000802
37109
92509
200
application/javascript
Script
https://www.lindsaysilberman.com/wp-content/plugins/social-pug/assets/dist/style-frontend-pro.1.19.1.css
h2
484.23400009051
547.16900014319
10642
101626
200
text/css
Stylesheet
https://scripts.mediavine.com/tags/lindsay-silberman.js
h2
503.34800011478
522.49000011943
19045
66102
200
application/javascript
Script
https://www.lindsaysilberman.com/wp-includes/js/jquery/jquery.min.js
h2
503.6370002199
540.37900012918
32938
89521
200
application/javascript
Script
https://www.lindsaysilberman.com/wp-content/themes/sitka/fonts/fontawesome-webfont.woff2?v=4.7.0
h2
485.09100009687
537.89000003599
78151
77160
200
font/woff2
Font
https://www.lindsaysilberman.com/wp-content/fonts/montserrat/JTUSjIg1_i6t8kCHKm459WlhzSTh89Y.woff
h2
485.58500013314
508.86900001206
18167
17180
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/lora/0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mvWc3ZyhTg.woff
h2
485.99100019783
512.83000013791
26533
25544
200
font/woff
Font
https://www.lindsaysilberman.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
h2
498.34700021893
516.26200019382
1492
1239
200
application/javascript
Script
https://z-na.associates-amazon.com/onetag/v2?MarketPlace=US&instanceId=124519c3-f4ec-438a-9ec7-329cf1133209
h2
503.91299999319
521.66700013913
499
23
200
text/javascript
Script
data
509.09000006504
509.24200005829
0
64
200
image/svg+xml
Image
data
511.26400008798
511.41900010407
0
69
200
image/svg+xml
Image
data
513.62000009976
513.7940000277
0
68
200
image/svg+xml
Image
data
515.88900014758
516.00000006147
0
66
200
image/svg+xml
Image
data
518.21200014092
518.33700016141
0
68
200
image/svg+xml
Image
https://www.lindsaysilberman.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
h2
520.97800001502
547.82300000079
3706
7890
200
application/javascript
Script
https://www.lindsaysilberman.com/wp-content/cache/min/1/46e14bcef8579ee91e2e19346a347573.js
h2
521.41100005247
549.71799999475
25338
86267
200
application/javascript
Script
https://scripts.mediavine.com/tags/2.73.1-fixBidderSyncs/wrapper.min.js?bust=169709059
h2
558.21800022386
589.91700015031
46431
146239
200
application/javascript
Script
https://exchange.mediavine.com/usersync.min.js?s2sVersion=production
h2
558.9480001945
811.9720001705
4664
13995
200
application/javascript
Script
https://keywords.mediavine.com/keyword/web.keywords.js?pageUrl=https://www.lindsaysilberman.com/
h2
559.2010000255
590.68500017747
724
384
200
text/html
Script
https://www.lindsaysilberman.com/wp-content/fonts/playfair-display/nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtXK-F2qO0g.woff
h2
574.39300022088
598.68900012225
25053
24064
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/montserrat/JTURjIg1_i6t8kCHKm45_dJE3gnD-Px3rCs.woff
h2
577.33100000769
599.18900020421
18708
17720
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/karla/qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lMZbLXGimS.woff
h2
577.51800003462
602.20300010405
15893
14904
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/poppins/pxiEyp8kv8JHgFVrJJfedHFHGPc.woff
h2
578.6120002158
601.49600007571
11522
10536
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/karla/qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlCV3lIb7X1HgGQ0tQ.woff
h2
583.06200010702
605.58800003491
16139
15152
200
font/woff
Font
https://assets.flodesk.com/universal.js?v=1641849980050
http/1.1
682.72700021043
744.28600003012
21715
58927
200
application/javascript
Script
https://assets.flodesk.com/universal.mjs?v=820924980
http/1.1
683.20200010203
835.38900013082
17690
46164
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
705.38699999452
710.08600015193
20631
50205
200
text/javascript
Script
https://assets.pinterest.com/js/pinit_main.js
h2
758.72000004165
996.67600006796
19065
68091
200
application/javascript
Script
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/LS-Main-Logo_teal-1.png
h2
762.58000009693
789.01599999517
4960
3972
200
image/webp
Image
https://www.lindsaysilberman.com/wp-content/uploads/2020/07/lindsay-silberman-amazon.jpg
h2
763.27300001867
823.4320001211
18058
17070
200
image/jpeg
Image
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/lindsay_silberman_travel_guide-3.jpg
h2
763.5490000248
795.70600017905
140666
139680
200
image/webp
Image
https://www.lindsaysilberman.com/wp-content/uploads/2020/07/Lindsay-Silberman-Beauty-Tips.jpg
h2
764.03500000015
790.32900021411
15909
14916
200
image/webp
Image
https://www.lindsaysilberman.com/wp-content/plugins/forget-about-shortcode-buttons/public/fonts/fontawesome-webfont.woff?v=4.0.3
h2
962.36700005829
997.67499999143
45421
44432
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/fonts/karla/qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aE0lMZbLXGimS.woff
h2
963.39200017974
987.95700003393
16001
15016
200
font/woff
Font
https://www.lindsaysilberman.com/wp-content/uploads/2021/07/best-amazon-finds-1140x760.jpg
h2
1014.4160001073
1044.6850000881
156662
155672
200
image/jpeg
Image
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=367228290&t=pageview&_s=1&dl=https%3A%2F%2Fwww.lindsaysilberman.com%2F&ul=en-us&de=UTF-8&dt=Lindsay%20Silberman%20%7C%20NYC%20Lifestyle%20Blogger&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=785690093&gjid=1595621576&cid=431961867.1641849980&tid=UA-90939214-1&_gid=1299929466.1641849980&_r=1&gtm=2ou150&did=dNDMyYj&gdid=dNDMyYj&z=1831066110
h2
1045.8230001386
1050.3760001156
623
2
200
text/plain
XHR
https://form.flodesk.com/forms/61a822bb6fd16bd0a4ddb27a
h2
1070.3590000048
1162.1940000914
5236
31932
200
text/html
XHR
https://form.flodesk.com/forms/5f189543626753002668ff39
h2
1071.0500001442
1188.0320000928
419
57
404
application/json
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j96&tid=UA-90939214-1&cid=431961867.1641849980&jid=785690093&gjid=1595621576&_gid=1299929466.1641849980&_u=YEBAAUAAAAAAAC~&z=974336663
h2
1112.1770001482
1116.3230000529
695
1
200
text/plain
XHR
https://fonts.googleapis.com/css?family=Montserrat:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i&display=swap
h2
1221.0890001152
1238.8250001241
2001
31778
200
text/css
Stylesheet
https://assets.flodesk.com/206.7ea484ce5c079bede463.js
http/1.1
1224.6540000197
1341.3639999926
6178
15123
200
application/javascript
Script
https://assets.flodesk.com/650.b7470aa52d152ef8b92d.js
http/1.1
1225.1630001701
1281.6670001484
4327
10345
200
application/javascript
Script
https://assets.flodesk.com/230.1ea5f0f94302f9053adb.js
http/1.1
1227.6550000533
1305.2240000106
11597
33537
200
application/javascript
Script
https://assets.flodesk.com/54.4749e9826da05043f33e.js
http/1.1
1228.4240000881
1308.8710000739
7297
22672
200
application/javascript
Script
https://usercontent.flodesk.com/ec4deb1f-4627-4707-8c63-45f221cd140a/upload/04032cbc-dfa3-4972-9605-2e74550a0032.jpeg
http/1.1
1233.8460001629
1366.283000214
382452
381953
200
image/jpeg
Image
https://www.lindsaysilberman.com/wp-content/fonts/karla/qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lMZbLXGimS.woff
h2
1235.7880000491
1261.8530001491
15891
14900
200
font/woff
Font
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_dJE3gnD_vx3rCs.woff2
h2
1273.8610000815
1277.4960000534
15056
14116
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
h2
1277.1870000288
1283.2270001527
15112
14172
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_cJD3gnD_vx3rCs.woff2
h2
1279.1570001282
1282.6540002134
15040
14100
200
font/woff2
Font
https://usercontent.flodesk.com/forms/5f189543626753002668ff39/data.json?v=820924980
http/1.1
1440.9170001745
1560.3750001173
4354
15761
200
application/json
XHR
https://usercontent.flodesk.com/forms/5f189543626753002668ff39/data.json?v=820924980
http/1.1
1338.5330000892
1440.2410001494
621
0
200
Preflight
https://fonts.googleapis.com/css?family=Montserrat:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i&display=swap
h2
1597.2260001581
1597.5380002055
2001
31778
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Raleway:300,300i,400,400i,700,700i
h2
1598.5980001278
1626.9830001984
1475
9531
200
text/css
Stylesheet
https://assets.flodesk.com/form.js?v=1641849980933
http/1.1
1601.1980001349
1691.929000197
28626
84144
200
application/javascript
Script
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_cJD3gnD_vx3rCs.woff2
h2
1609.6780002117
1609.9260000046
15040
14100
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
h2
1610.3890000377
1610.5150000658
15112
14172
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_dJE3gnD_vx3rCs.woff2
h2
1612.1600000188
1612.4150000978
15056
14116
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v18/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
h2
1617.1190000605
1620.7860000432
15092
14152
200
font/woff2
Font
https://log.pinterest.com/?type=pidget&guid=FAsb6CwTa4of&tv=2021110201&event=init&sub=www&button_count=0&follow_count=0&pin_count=0&profile_count=0&board_count=0&section_count=0&xload=1&lang=en&nvl=en-US&via=https%3A%2F%2Fwww.lindsaysilberman.com%2F&viaSrc=canonical
h2
2214.2849999946
2247.4480001256
534
0
200
text/plain
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)
521.604
10.075
537.685
7.184
549.895
20.685
579.938
10.312
593.489
17.215
610.719
48.732
677.441
17.754
696.716
10.154
707.756
19.532
727.515
10.086
741.215
15.076
759.268
49.082
817.461
9.005
834.256
106.009
940.327
5.306
947.066
21.415
973.211
66.662
1040.03
10.442
1050.612
10.097
1065.491
32.468
1098.007
23.923
1130.2
20.586
1151.765
7.252
1165.436
79.661
1245.918
11.632
1257.603
9.109
1266.957
10.128
1280.059
19.673
1300.497
8.286
1311.06
33.209
1355.387
16.893
1378.107
11.285
1395.29
10.914
1419.944
28.043
1448.067
6.794
1612.315
42.126
1654.508
24.716
1684.697
11.153
1751.288
27.635
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

Total Blocking Time — 550 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 — 210 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 3.6 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused CSS — Potential savings of 102 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lindsaysilberman.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://www.lindsaysilberman.com/wp-content/cache/min/1/95c8d3aa2b915d26a3cbec15bb7e2d76.css
96840
91922
span.PIN_1641849980578_embed_grid { width: 100%; max-width: 257px; min-width: 140px; ... } ...
12244
12244
Reduce unused JavaScript — Potential savings of 26 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://scripts.mediavine.com/tags/2.73.1-fixBidderSyncs/wrapper.min.js?bust=169709059
46431
26639
Serve images in next-gen formats — Potential savings of 176 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://usercontent.flodesk.com/ec4deb1f-4627-4707-8c63-45f221cd140a/upload/04032cbc-dfa3-4972-9605-2e74550a0032.jpeg
381953
123200.6
https://www.lindsaysilberman.com/wp-content/uploads/2021/07/best-amazon-finds-1140x760.jpg
155672
56681.4
Avoid serving legacy JavaScript to modern browsers — Potential savings of 46 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://assets.flodesk.com/form.js?v=1641849980933
13904
https://assets.flodesk.com/universal.js?v=1641849980050
12500
https://assets.flodesk.com/230.1ea5f0f94302f9053adb.js
11967
https://assets.flodesk.com/206.7ea484ce5c079bede463.js
8893
https://www.lindsaysilberman.com/
167
https://assets.flodesk.com/54.4749e9826da05043f33e.js
65
https://www.lindsaysilberman.com/wp-content/cache/min/1/46e14bcef8579ee91e2e19346a347573.js
49
Serve static assets with an efficient cache policy — 4 resources found
Lindsaysilberman.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://z-na.associates-amazon.com/onetag/v2?MarketPlace=US&instanceId=124519c3-f4ec-438a-9ec7-329cf1133209
0
499
https://assets.pinterest.com/js/pinit_main.js
264000
19065
https://www.google-analytics.com/analytics.js
7200000
20631
https://www.lindsaysilberman.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000
1492
Avoid an excessive DOM size — 846 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
846
Maximum DOM Depth
15
Maximum Child Elements
28
Reduce JavaScript execution time — 1.7 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.lindsaysilberman.com/
1500.188
83.44
15.504
https://www.lindsaysilberman.com/wp-includes/js/jquery/jquery.min.js
950.472
424.2
6.056
https://assets.flodesk.com/54.4749e9826da05043f33e.js
555.572
143
1.836
Unattributable
450.924
61.536
0.88
https://assets.flodesk.com/230.1ea5f0f94302f9053adb.js
211.168
148.024
8.368
https://assets.flodesk.com/universal.js?v=1641849980050
149.888
123.392
5.384
https://www.google-analytics.com/analytics.js
143.624
124.116
4.308
https://scripts.mediavine.com/tags/2.73.1-fixBidderSyncs/wrapper.min.js?bust=169709059
141.484
125.332
10.376
https://scripts.mediavine.com/tags/lindsay-silberman.js
131.34
121.916
5.84
https://www.googletagmanager.com/gtag/js?id=UA-90939214-1
114.592
97.584
8.904
https://assets.flodesk.com/form.js?v=1641849980933
110.3
87.832
7.388
https://assets.pinterest.com/js/pinit_main.js
77.04
66.992
5.056

Metrics

First Contentful Paint — 3.6 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 12.2 s
The time taken for the page to become fully interactive.
Speed Index — 5.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 10.6 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.646
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Lindsaysilberman.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lindsaysilberman.com/
630
https://lindsaysilberman.com/
480
https://www.lindsaysilberman.com/
0
Minimize main-thread work — 4.7 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
1744.2
Style & Layout
1230.372
Other
1010.06
Rendering
386.244
Parse HTML & CSS
226.18
Script Parsing & Compilation
95.764
Garbage Collection
28.812
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Avoid `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.
Source
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.lindsaysilberman.com/wp-content/uploads/2020/08/LS-Main-Logo_teal-1.png
https://www.lindsaysilberman.com/wp-content/uploads/2020/08/LS-Main-Logo_teal-1.png
First Contentful Paint (3G) — 7331 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
80

Accessibility

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

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.
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"]`
Lindsaysilberman.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
`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.

Contrast

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

Navigation

`[id]` attributes on active, focusable elements are not 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.
Failing Elements
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

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 lindsaysilberman.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.
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
jQuery
3.6.0
WordPress
5.8.3
core-js
core-js-global@3.16.0; core-js-global@3.16.0; core-js-pure@3.15.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://scripts.mediavine.com/tags/lindsay-silberman.js
https://scripts.mediavine.com/tags/launcher.min.js.map;
https://scripts.mediavine.com/tags/2.73.1-fixBidderSyncs/wrapper.min.js?bust=169709059
https://scripts.mediavine.com/tags/2.73.1-fixBidderSyncs/wrapper.min.js.map
https://exchange.mediavine.com/usersync.min.js?s2sVersion=production
https://exchange.mediavine.com/usersync.min.js.map
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://lindsaysilberman.com/
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
200 x 150 (1.33)
300 x 150 (2.00)

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for lindsaysilberman.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 lindsaysilberman.com on mobile screens.
Document uses legible font sizes — 98.75% 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
#inner-wrapper .promo-style2 .promo-item h5
0.58%
11px
h3
0.22%
0px
.fd-h1
0.19%
0px
.fd-h2
0.11%
0px
.fd-div
0.10%
0px
.post-cats span
0.02%
10px
.sitka-pagination .page-numbers.prev, .sitka-pagination .page-numbers.next
0.02%
11px
0.02%
10px
98.75%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the 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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

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

PWA Optimized

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 lindsaysilberman.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

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
Content is not 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.
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: 172.67.140.219
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
Cloudflare, 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
TUCOWS, INC. 199.16.172.52
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 6th July, 2021
Valid To: 5th July, 2022
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 15864257152617958776484831699563933463
Serial Number (Hex): 0BEF58442111461713390BA4373B6F17
Valid From: 6th July, 2024
Valid To: 5th July, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Jul 6 15:20:21.040 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:81:FB:E1:F4:4C:5F:65:16:21:07:68:
D9:34:54:7A:D9:99:76:43:D9:0D:08:D7:2D:12:C1:88:
EA:1F:63:9A:64:02:20:3D:CC:02:29:04:22:13:4B:FE:
A4:2F:43:62:EC:DB:71:D1:43:70:E4:ED:DA:C4:E9:54:
F0:A1:B9:D3:39:09:38
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 51:A3:B0:F5:FD:01:79:9C:56:6D:B8:37:78:8F:0C:A4:
7A:CC:1B:27:CB:F7:9E:88:42:9A:0D:FE:D4:8B:05:E5
Timestamp : Jul 6 15:20:21.127 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:73:B0:8B:6D:09:06:3D:64:7F:5D:A8:17:
15:44:22:C6:E2:A8:CA:E6:82:9C:FB:61:38:6D:88:59:
D3:42:8E:93:02:21:00:FD:77:A9:8C:FE:2C:1E:C3:E6:
F5:F7:7D:45:40:F5:49:CC:55:1A:3D:77:D8:54:8E:86:
47:AA:1F:4D:E8:AD:F1
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Jul 6 15:20:21.110 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:94:C9:BB:62:D3:45:28:CE:EF:EE:7F:
D4:A7:97:F6:7C:8F:66:54:ED:D1:3C:FA:E2:DC:6C:C3:
4E:D5:19:1E:42:02:20:63:05:5B:B7:F2:C9:F1:AB:3F:
F2:E0:C3:B2:14:09:FE:75:B3:63:0E:0B:D5:F8:01:5B:
B3:39:FC:97:6B:60:13
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.lindsaysilberman.com
DNS:lindsaysilberman.com
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 301 Moved Permanently
Date: 10th January, 2022
Content-Type: text/html
Server: cloudflare
Connection: keep-alive
location: https://lindsaysilberman.com/
host-header: 8441280b0c35cbc1147f8ba998a563a7
x-https-enforce: 1
x-proxy-cache-info: DT:1
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=LI8Bfh8lYokB%2B5mF2frRFTniA7L57k12ty5jMzpMUJCVPtzjquwkfFOLmm3I4hEMZhlXcAkr%2FoZ3M65iwSyqCsYVfIONECXaCOfc%2FxCU4%2BEuXVY5eeWdS6MzqxgJRV8htY5Zlt7n7A%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 6cb8fb017e4432e2-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400

Whois Lookup

Created: 22nd March, 2016
Changed: 7th March, 2021
Expires: 22nd March, 2022
Registrar: TUCOWS, INC.
Status: ok
Nameservers: dakota.ns.cloudflare.com
harlee.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: NY
Owner Country: US
Owner Phone: REDACTED FOR PRIVACY
Owner Email: https://tieredaccess.com/contact/8fb019ea-e56a-479d-9269-9f0ea435449e
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Full Whois: Domain Name: LINDSAYSILBERMAN.COM
Registry Domain ID: 2014482213_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://tucowsdomains.com
Updated Date: 2021-03-07T06:14:22
Creation Date: 2016-03-22T02:25:32
Registrar Registration Expiration Date: 2022-03-22T02:25:32
Registrar: TUCOWS, INC.
Registrar IANA ID: 69
Reseller: SG Hosting Inc.
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID:
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: NY
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext:
Registrant Email: https://tieredaccess.com/contact/8fb019ea-e56a-479d-9269-9f0ea435449e
Registry Admin ID:
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext:
Admin Email: REDACTED FOR PRIVACY
Registry Tech ID:
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext:
Tech Email: REDACTED FOR PRIVACY
Name Server: harlee.ns.cloudflare.com
Name Server: dakota.ns.cloudflare.com
DNSSEC: unsigned
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-01-10T21:25:56Z <<<

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

Registration Service Provider:
SG Hosting Inc., tucows@domains.siteground.com
+1.8008289231
This company may be contacted for domain login/passwords,
DNS/Nameserver changes, and general domain support questions.

The Data in the Tucows Registrar WHOIS database is provided to you by Tucows
for information purposes only, and may be used to assist you in obtaining
information about or related to a domain name's registration record.

Tucows makes this information available "as is," and does not guarantee its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
a) allow, enable, or otherwise support the transmission by e-mail,
telephone, or facsimile of mass, unsolicited, commercial advertising or
solicitations to entities other than the data recipient's own existing
customers; or (b) enable high volume, automated, electronic processes that
send queries or data to the systems of any Registry Operator or
ICANN-Accredited registrar, except as reasonably necessary to register
domain names or modify existing registrations.

The compilation, repackaging, dissemination or other use of this Data is
expressly prohibited without the prior written consent of Tucows.

Tucows reserves the right to terminate your access to the Tucows WHOIS
database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this
policy.

Tucows reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by these terms.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.

Nameservers

Name IP Address
dakota.ns.cloudflare.com 172.64.35.79
harlee.ns.cloudflare.com 172.64.34.238
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address