lifewithheidi.com

lifewithheidi.com is SSL secured

Free website and domain report on lifewithheidi.com

Last Updated: 23rd March, 2021 Update Now
Overview

Snoop Summary for lifewithheidi.com

This is a free and comprehensive report about lifewithheidi.com. The domain lifewithheidi.com is currently hosted on a server located in United States with the IP address 162.248.188.100, where USD is the local currency and the local language is English. Our records indicate that lifewithheidi.com is owned/operated by Save More Spend Less with Heidi. Lifewithheidi.com has the potential to be earning an estimated $13 USD per day from advertising revenue. If lifewithheidi.com was to be sold it would possibly be worth $9,749 USD (based on the daily revenue potential of the website over a 24 month period). Lifewithheidi.com receives an estimated 4,681 unique visitors every day - a large amount of traffic! This report was last updated 23rd March, 2021.

About lifewithheidi.com

Site Preview: lifewithheidi.com lifewithheidi.com
Title: Homepage ⋆ Life With Heidi
Description: Joomla!
Keywords and Tags: blogs, wiki
Related Terms: heidi, heidi klum
Fav Icon:
Age: Over 8 years old
Domain Created: 9th November, 2015
Domain Updated: 11th October, 2020
Domain Expires: 9th November, 2021
Review

Snoop Score

2/5

Valuation

$9,749 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 128,711
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: 4,681
Monthly Visitors: 142,475
Yearly Visitors: 1,708,565
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $13 USD
Monthly Revenue: $406 USD
Yearly Revenue: $4,869 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: lifewithheidi.com 17
Domain Name: lifewithheidi 13
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 5.02 seconds
Load Time Comparison: Faster than 8% of sites

PageSpeed Insights

Avg. (All Categories) 71
Performance 47
Accessibility 98
Best Practices 80
SEO 83
Progressive Web App 45
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.lifewithheidi.com
Updated: 23rd March, 2021

3.48 seconds
First Contentful Paint (FCP)
13%
55%
32%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
47

Performance

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

Metrics

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

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lifewithheidi.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 46 KiB
Images can slow down the page's load time. Lifewithheidi.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Create-DIY-683x1024.jpg
82937
32214
https://www.lifewithheidi.com/wp-content/uploads/2019/12/heidi.jpg
41180
15044
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Lifewithheidi.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lifewithheidi.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 3 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lifewithheidi.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.lifewithheidi.com/wp-content/plugins/genesis-responsive-slider/assets/js/jquery.flexslider.js?ver=1.0.1
5966
2918
Remove unused CSS — Potential savings of 48 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lifewithheidi.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.lifewithheidi.com/wp-content/litespeed/cssjs/bdadc.css?8c3b0
35645
35393
https://fonts.googleapis.com/css?family=Nanum+Myeongjo:wght@400;800
13959
13959
Remove unused JavaScript — Potential savings of 52 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
40514
30001
https://www.lifewithheidi.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
30654
22969
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 39 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Create-DIY-683x1024.jpg
82937
40127
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lifewithheidi.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://lifewithheidi.com/wp-content/themes/restored316-farmhouse/config/import/images/large-bg.jpg
0

Diagnostics

Avoids enormous network payloads — Total size was 999 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://lifewithheidi.com/wp-content/themes/restored316-farmhouse/config/import/images/large-bg.jpg
199140
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Create-DIY-683x1024.jpg
83254
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/MonologueScript-Regular.woff2
62889
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightDispProBook-Regular.woff2
41498
https://www.lifewithheidi.com/wp-content/uploads/2019/12/heidi.jpg
41497
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/lib/gutenberg/fonts/FreightDispProBook-Regular.woff2
41317
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
40514
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightBigProLight-Italic.woff2
39582
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightBigProLight-Regular.woff2
38386
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/lib/gutenberg/fonts/FreightBigProLight-Regular.woff2
38205
Uses efficient cache policy on static assets — 1 resource found
Lifewithheidi.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
19610
Avoids an excessive DOM size — 713 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
713
Maximum DOM Depth
img
20
Maximum Child Elements
14
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Lifewithheidi.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.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.lifewithheidi.com/
1827.037
28.412
3.268
Unattributable
567.963
1.443
0.181
https://www.google-analytics.com/analytics.js
299.517
295.03
1.639
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
214.96
110.258
102.14
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/bf3f7.js?4e8d7
92.879
0.024
92.693
https://www.lifewithheidi.com/wp-content/plugins/litespeed-cache/assets/js/webfontloader.min.js
83.05
80.285
2.114
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/d1203.css?0dfe1
76.871
0
0
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/84ded.css?3b694
75.315
0
0
Keep request counts low and transfer sizes small — 60 requests • 999 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
60
1023434
Font
14
376264
Image
8
332292
Script
17
165394
Stylesheet
16
123239
Document
1
24091
Other
4
2154
Media
0
0
Third-party
16
191596
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.043018207855974
0.040787634115294
0.010121931260229
0.0035426759410802
0.00010064108878382
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 19 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.lifewithheidi.com/
859
385
https://www.google-analytics.com/analytics.js
2634
296
https://www.lifewithheidi.com/
1563
152
https://www.lifewithheidi.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
1320
140
https://www.lifewithheidi.com/
2021
140
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/bf3f7.js?4e8d7
1460
103
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
2174
101
https://www.lifewithheidi.com/
1784
100
Unattributable
258
89
Unattributable
624
80
Unattributable
347
78
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
2275
78
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/d1203.css?0dfe1
782
77
https://www.lifewithheidi.com/wp-content/plugins/litespeed-cache/assets/js/webfontloader.min.js
1244
76
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/84ded.css?3b694
707
75
Unattributable
1897
72
Unattributable
1715
69
Unattributable
190
68
https://www.lifewithheidi.com/
1969
52
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

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

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://lifewithheidi.com/
http/1.1
0
171.22199991718
306
0
301
text/html
https://lifewithheidi.com/
http/1.1
171.71599995345
1113.9730000868
526
0
301
text/html
https://www.lifewithheidi.com/
h2
1114.9980002083
1995.0210000388
24091
115585
200
text/html
Document
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/b64c2.css?c4f5a
h2
2005.7990001515
2299.2239999585
1711
2968
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/973ac.css?474dd
h2
2006.07400015
2196.8780001625
10202
47938
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/84ded.css?3b694
h2
2006.2060002238
2115.9240002744
3023
16877
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/7d67c.css?834f5
h2
2006.4710001461
2310.4610000737
6197
26875
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/00bb9.css?77406
h2
2006.6720000468
2194.2730001174
8500
58180
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/9df01.css?78468
h2
2007.1169999428
2303.8880000822
6620
45086
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/85f87.css?dd01e
h2
2007.340000011
2303.5269998945
3170
19156
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/e2568.css?db9b2
h2
2007.8230001964
2304.4740003534
1162
2600
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/d1203.css?0dfe1
h2
2007.9880002886
2305.9060000814
4017
22640
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/ed881.css?c3c09
h2
2008.1390002742
2304.9130002037
7861
68082
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/bdadc.css?8c3b0
h2
2008.5249999538
2313.2299999706
35645
59040
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/743fe.css?16e80
h2
2008.7800002657
2309.3560002744
3201
13602
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/48e59.css?184d9
h2
2008.9320000261
2213.0980002694
1156
2862
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
h2
2009.1289998963
2224.5590002276
30654
89496
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/bf3f7.js?4e8d7
h2
2009.442999959
2396.2139999494
35203
123652
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/plugins/litespeed-cache/assets/js/webfontloader.min.js
h2
2009.5999999903
2302.9510001652
5196
12098
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/MonologueScript-Regular.woff2
h2
2017.8820001893
2196.0280002095
62889
62572
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightDispProBook-Regular.woff2
h2
2099.6719999239
2394.9850001372
41498
41000
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightBigProLight-Italic.woff2
h2
2100.1400002278
2395.6650001928
39582
39084
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightBigProLight-Regular.woff2
h2
2100.316000171
2397.1560001373
38386
37888
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/style.css?ver=1.0.0
h2
2100.4510000348
2309.7950001247
8227
38081
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/plugins/cookie-law-info/public/js/cookie-law-info-public.js?ver=2.0.1
h2
2100.5800003186
2216.1730001681
8467
35807
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/plugins/social-pug/assets/dist/front-end-pro-jquery.2.13.0.js?ver=2.13.0
h2
2100.7400001399
2306.7270000465
6897
22826
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/plugins/genesis-blocks/dist/assets/js/dismiss.js?ver=1616519659
h2
2100.9360002354
2309.0340001509
929
923
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/genesis/lib/js/menu/superfish.min.js?ver=1.7.10
h2
2101.0779999197
2307.8250000253
2285
4499
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/genesis/lib/js/menu/superfish.args.min.js?ver=3.3.3
h2
2101.2130002491
2312.5460003503
640
132
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/genesis/lib/js/skip-links.min.js?ver=3.3.3
h2
2101.3770001009
2212.4370001256
553
386
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/js/responsive-menus.min.js?ver=1611166859
h2
2101.5039999038
2311.252000276
2436
6943
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/js/block-effects.js?ver=1611166859
h2
2101.6390002333
2397.7330001071
2005
4477
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/js/smooth-scroll.js?ver=1611166859
h2
2101.7860001884
2306.2100000679
1064
1163
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/js/top-banner.min.js?ver=1611166859
h2
2102.3670001887
2307.4570000172
1766
3356
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/plugins/genesis-responsive-slider/assets/js/jquery.flexslider.js?ver=1.0.1
h2
2102.5760001503
2308.2250002772
5966
27245
200
application/javascript
Script
https://www.lifewithheidi.com/wp-includes/js/wp-embed.min.js?ver=5.7
h2
2102.7470002882
2305.5420001037
1209
1426
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
h2
2629.1840001941
2700.5110001191
40514
100873
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/uploads/2021/01/cropped-LWH-1.png
h2
2629.3299999088
2697.3810000345
5882
5567
200
image/png
Image
https://www.lifewithheidi.com/wp-content/plugins/mediavine-create/client/build/style.1.6.6.css?ver=1.6.6
h2
2629.0299999528
2699.9050001614
8588
58321
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Nanum+Myeongjo:wght@400;800
h2
2495.6060000695
2594.3330000155
13959
57576
200
text/css
Stylesheet
https://lifewithheidi.com/wp-content/themes/restored316-farmhouse/config/import/images/large-bg.jpg
h2
2703.8890002295
3096.3980001397
199140
198641
200
image/jpeg
Image
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/images/searchicon.png
h2
2717.426000163
2807.2629999369
715
401
200
image/png
Image
data
2816.695000045
3913.8340000063
31728
31728
200
application/x-font-woff
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/lib/gutenberg/fonts/FreightDispProBook-Regular.woff2
h2
2830.4429999553
2923.6190002412
41317
41000
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/lib/gutenberg/fonts/FreightBigProLight-Regular.woff2
h2
2830.6189998984
2996.5850003064
38205
37888
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/uploads/2019/12/heidi.jpg
h2
3405.281000305
3496.0650000721
41497
41180
200
image/jpeg
Image
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Create-DIY-683x1024.jpg
h2
3408.368000295
3595.8870002069
83254
82937
200
image/jpeg
Image
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.119.woff2
h2
3603.8689999841
3712.0300000533
10347
9784
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.117.woff2
h2
3621.7350000516
3708.8609999046
14184
13620
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.118.woff2
h2
3622.0309999771
3710.7069999911
12959
12408
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.99.woff2
h2
3622.212999966
3709.4930000603
14443
13892
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.114.woff2
h2
3699.3070002645
3711.5569999442
15567
15004
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.115.woff2
h2
3718.3779999614
3732.6839999296
15096
14532
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.109.woff2
h2
3723.079000134
3794.17499993
16496
15932
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.116.woff2
h2
3807.7040002681
3814.2880001105
15295
14744
200
font/woff2
Font
https://www.google-analytics.com/analytics.js
h2
5013.4360003285
5019.6810001507
19610
47332
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j88&a=1983293544&t=pageview&_s=1&dl=https%3A%2F%2Fwww.lifewithheidi.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%E2%8B%86%20Life%20With%20Heidi&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUABAAAAAC~&jid=457941406&gjid=77967828&cid=1642864002.1616520560&tid=UA-30348332-1&_gid=592359044.1616520560&_r=1&gtm=2ou3h0&z=2026179830
h2
5325.1350000501
5398.7449998967
625
2
200
text/plain
XHR
https://www.google-analytics.com/collect?v=1&_v=j88&a=1983293544&t=pageview&_s=2&dl=https%3A%2F%2Fwww.lifewithheidi.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%E2%8B%86%20Life%20With%20Heidi&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUABAAAAAC~&jid=&gjid=&cid=1642864002.1616520560&tid=UA-30348332-1&_gid=592359044.1616520560&gtm=2ou3h0&z=626975330
h2
5403.1199999154
5407.8959999606
601
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j88&a=1983293544&t=pageview&_s=3&dl=https%3A%2F%2Fwww.lifewithheidi.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%E2%8B%86%20Life%20With%20Heidi&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUABAAAAAC~&jid=&gjid=&cid=1642864002.1616520560&tid=UA-30348332-1&_gid=592359044.1616520560&gtm=2ou3h0&z=2042941937
h2
5403.355000075
5408.4360003471
601
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j88&a=1983293544&t=pageview&_s=4&dl=https%3A%2F%2Fwww.lifewithheidi.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%E2%8B%86%20Life%20With%20Heidi&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUABAAAAAC~&jid=&gjid=&cid=1642864002.1616520560&tid=UA-30348332-1&_gid=592359044.1616520560&gtm=2ou3h0&z=106914826
h2
5404.8550003208
5408.786999993
602
35
200
image/gif
Image
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j88&tid=UA-30348332-1&cid=1642864002.1616520560&jid=457941406&gjid=77967828&_gid=592359044.1616520560&_u=IEBAAUAAAAAAAC~&z=1119795898
h2
5406.8050002679
5411.521000322
697
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
2094.449
14.198
2109.878
80.447
2215.553
75.315
2295.684
5.886
2321.988
68.459
2414.783
76.871
2514.405
76.375
2591.104
140.424
2731.547
770.465
3505.916
7.78
3514.354
103.008
3617.379
303.633
3921.054
68.717
3994.034
5.485
4002.604
9.342
4012.072
89.351
4101.729
199.441
4301.186
13.032
4318.049
72.404
4402.963
104.191
4512.298
78.049
4591.561
5.93
4597.505
11.893
4609.584
280.288
4890.401
13.421
4903.837
101.311
5005.23
8.89
5014.137
78.034
5098.124
11.297
5203.399
295.911
6664.546
24.932
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 1.3 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 2.2 s
The timing of the largest text or image that is painted.
Time to Interactive — 2.8 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 2.8 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 1.3 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 70 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive lifewithheidi.com as laggy when the latency is higher than 0.05 seconds.

Opportunities

Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Lifewithheidi.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lifewithheidi.com/
190
https://lifewithheidi.com/
150
https://www.lifewithheidi.com/
0

Diagnostics

Minimize main-thread work — 3.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
1359.266
Other
679.803
Script Evaluation
538.061
Rendering
299.393
Parse HTML & CSS
218.064
Script Parsing & Compilation
204.206
Garbage Collection
1.998

Metrics

Speed Index — 3.7 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 680 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

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

Opportunities

Reduce initial server response time — Root document took 880 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.lifewithheidi.com/
881.019

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.119.woff2
108.16100006923
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.117.woff2
87.125999853015
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.118.woff2
88.676000013947
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.99.woff2
87.280000094324
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.114.woff2
12.249999679625
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.115.woff2
14.305999968201
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.109.woff2
71.095999795943
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.116.woff2
6.5839998424053
Reduce the impact of third-party code — Third-party code blocked the main thread for 300 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)
22039
241.584
40514
60.011
128346
0
697
0
98

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Lifewithheidi.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that lifewithheidi.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.

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
WebFont Loader
WordPress
5.7
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.
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://lifewithheidi.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

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
SyntaxError: Unexpected identifier
83

SEO

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

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

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

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of lifewithheidi.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) 71
Performance 58
Accessibility 98
Best Practices 73
SEO 86
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.lifewithheidi.com
Updated: 23rd March, 2021

4.06 seconds
First Contentful Paint (FCP)
3%
57%
40%

0.26 seconds
First Input Delay (FID)
6%
89%
5%

Simulate loading on mobile
58

Performance

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

Metrics

Total Blocking Time — 30 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.065
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 90 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive lifewithheidi.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://lifewithheidi.com/
http/1.1
0
177.60000005364
306
0
301
text/html
https://lifewithheidi.com/
http/1.1
178.11500001699
1055.596999824
526
0
301
text/html
https://www.lifewithheidi.com/
h2
1056.2579999678
1731.7669996992
23910
115585
200
text/html
Document
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/b64c2.css?c4f5a
h2
1740.9939998761
1784.897999838
1530
2968
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/973ac.css?474dd
h2
1741.2429996766
1790.0350000709
10202
47938
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/84ded.css?3b694
h2
1741.4359999821
1788.7909999117
3023
16877
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/7d67c.css?834f5
h2
1741.5620000102
1834.9939999171
6016
26875
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/00bb9.css?77406
h2
1741.8849999085
1793.6599999666
8500
58180
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/9df01.css?78468
h2
1742.0850000344
1791.9109999202
6439
45086
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/85f87.css?dd01e
h2
1742.4159999937
1833.8210000657
2989
19156
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/e2568.css?db9b2
h2
1742.8659996949
1831.1499999836
981
2600
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/d1203.css?0dfe1
h2
1743.1890000589
1877.0570000634
3836
22640
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/ed881.css?c3c09
h2
1743.3980000205
1835.630999878
7680
68082
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/bdadc.css?8c3b0
h2
1743.5729997233
1837.2559999116
35464
59040
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/743fe.css?16e80
h2
1743.8269997947
1790.7949998043
3020
13602
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/48e59.css?184d9
h2
1743.9739997499
1830.7550000027
1156
2862
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
h2
1744.1940000281
1875.2669999376
30654
89496
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/litespeed/cssjs/bf3f7.js?4e8d7
h2
1744.3539998494
1876.5589999966
35022
123652
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/plugins/litespeed-cache/assets/js/webfontloader.min.js
h2
1744.4909997284
1874.7759996913
5015
12098
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/MonologueScript-Regular.woff2
h2
1749.3779999204
1834.3079998158
62889
62572
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightDispProBook-Regular.woff2
h2
1749.6529999189
1917.5909999758
41317
41000
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightBigProLight-Italic.woff2
h2
1750.0089998357
1918.1319996715
39401
39084
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightBigProLight-Regular.woff2
h2
1750.2449997701
1918.7859999947
38205
37888
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/style.css?ver=1.0.0
h2
1750.4399996251
1836.1749998294
8046
38081
200
text/css
Stylesheet
https://www.lifewithheidi.com/wp-content/plugins/cookie-law-info/public/js/cookie-law-info-public.js?ver=2.0.1
h2
1750.77399984
1836.8519996293
8467
35807
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/plugins/social-pug/assets/dist/front-end-pro-jquery.2.13.0.js?ver=2.13.0
h2
1751.215999946
1870.5469998531
6716
22826
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/plugins/genesis-blocks/dist/assets/js/dismiss.js?ver=1616519659
h2
1751.4589997008
1832.9880000092
748
923
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/genesis/lib/js/menu/superfish.min.js?ver=1.7.10
h2
1751.6159997322
1871.1039996706
2104
4499
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/genesis/lib/js/menu/superfish.args.min.js?ver=3.3.3
h2
1751.8130000681
1833.3339998499
459
132
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/genesis/lib/js/skip-links.min.js?ver=3.3.3
h2
1751.9449996762
1833.5589999333
553
386
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/js/responsive-menus.min.js?ver=1611166859
h2
1752.2359997965
1871.412999928
2255
6943
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/js/block-effects.js?ver=1611166859
h2
1752.4239998311
1918.5239998624
1824
4477
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/js/smooth-scroll.js?ver=1611166859
h2
1752.536999993
1871.7029998079
883
1163
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/js/top-banner.min.js?ver=1611166859
h2
1752.7779997326
1872.3399997689
1585
3356
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/plugins/genesis-responsive-slider/assets/js/jquery.flexslider.js?ver=1.0.1
h2
1753.100999631
1872.0309999771
5785
27245
200
application/javascript
Script
https://www.lifewithheidi.com/wp-includes/js/wp-embed.min.js?ver=5.7
h2
1753.3029997721
1832.5829999521
1028
1426
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
h2
1900.6949998438
1924.3729999289
40514
100873
200
application/javascript
Script
https://www.lifewithheidi.com/wp-content/uploads/2021/01/cropped-LWH-1.png
h2
1900.8430000395
1959.5809997991
5882
5567
200
image/png
Image
https://www.lifewithheidi.com/wp-content/plugins/mediavine-create/client/build/style.1.6.6.css?ver=1.6.6
h2
1900.510000065
1949.3519999087
8588
58321
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Nanum+Myeongjo:wght@400;800
h2
1880.9710000642
1905.5809997953
13959
57576
200
text/css
Stylesheet
https://lifewithheidi.com/wp-content/themes/restored316-farmhouse/config/import/images/large-bg.jpg
h2
1916.9580000453
2089.1089998186
198959
198641
200
image/jpeg
Image
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/images/searchicon.png
h2
1927.3109999485
1970.6699997187
715
401
200
image/png
Image
data
1936.0059997998
2001.9509997219
31728
31728
200
application/x-font-woff
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/lib/gutenberg/fonts/FreightDispProBook-Regular.woff2
h2
1937.2849999927
1982.6179998927
41317
41000
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/lib/gutenberg/fonts/FreightBigProLight-Regular.woff2
h2
1937.6329998486
1984.3480000272
38205
37888
200
font/woff2
Font
https://www.lifewithheidi.com/wp-content/uploads/2019/12/heidi.jpg
h2
1987.5949998386
2033.0329998396
41497
41180
200
image/jpeg
Image
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Create-DIY-scaled.jpg
h2
1987.7780000679
2173.0479998514
258454
258136
200
image/jpeg
Image
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Recipes.png
h2
1987.9419999197
2273.0890000239
2508475
2508157
200
image/png
Image
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Travel.jpg
h2
1988.0929999053
2230.3639999591
1924573
1924254
200
image/jpeg
Image
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Frugal-Living.png
h2
1988.2869999856
2347.1099999733
6014781
6014463
200
image/png
Image
https://www.lifewithheidi.com/wp-content/uploads/2021/03/Planning-A-Budget-Bathroom-Makeover.jpg
h2
1988.4559996426
2074.595999904
69006
68689
200
image/jpeg
Image
https://www.lifewithheidi.com/wp-content/uploads/2021/03/7-Benefits-Of-Buying-A-New-Build-Property-.jpg
h2
1988.6209997348
2081.7080000415
79607
79290
200
image/jpeg
Image
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.119.woff2
h2
2023.5919998959
2027.720999904
10347
9784
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.117.woff2
h2
2025.3570000641
2029.1299996898
14184
13620
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.118.woff2
h2
2028.3849998377
2032.0629999042
12972
12408
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.99.woff2
h2
2028.9059998468
2031.6490000114
14456
13892
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.114.woff2
h2
2035.7729997486
2039.0949998982
15568
15004
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.115.woff2
h2
2041.4859997109
2056.2499999069
15083
14532
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.109.woff2
h2
2043.5969997197
2047.0019998029
16495
15932
200
font/woff2
Font
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.116.woff2
h2
2055.4939997382
2059.1019997373
15308
14744
200
font/woff2
Font
https://www.google-analytics.com/analytics.js
h2
2147.551999893
2151.5969997272
19609
47332
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j88&a=2051455928&t=pageview&_s=1&dl=https%3A%2F%2Fwww.lifewithheidi.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%E2%8B%86%20Life%20With%20Heidi&sd=24-bit&sr=360x640&vp=1440x2560&je=0&_u=IEBAAUABAAAAAC~&jid=1422332058&gjid=1918557881&cid=1269297094.1616520627&tid=UA-30348332-1&_gid=1837988999.1616520627&_r=1&gtm=2ou3h0&z=1358400731
h2
2223.884999752
2232.951999642
625
2
200
text/plain
XHR
https://www.google-analytics.com/collect?v=1&_v=j88&a=2051455928&t=pageview&_s=2&dl=https%3A%2F%2Fwww.lifewithheidi.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%E2%8B%86%20Life%20With%20Heidi&sd=24-bit&sr=360x640&vp=1440x2560&je=0&_u=IEBAAUABAAAAAC~&jid=&gjid=&cid=1269297094.1616520627&tid=UA-30348332-1&_gid=1837988999.1616520627&gtm=2ou3h0&z=920714560
h2
2235.7899998315
2239.3069998361
602
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j88&a=2051455928&t=pageview&_s=3&dl=https%3A%2F%2Fwww.lifewithheidi.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%E2%8B%86%20Life%20With%20Heidi&sd=24-bit&sr=360x640&vp=1440x2560&je=0&_u=IEBAAUABAAAAAC~&jid=&gjid=&cid=1269297094.1616520627&tid=UA-30348332-1&_gid=1837988999.1616520627&gtm=2ou3h0&z=1361854445
h2
2236.530999653
2239.8629998788
602
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j88&a=2051455928&t=pageview&_s=4&dl=https%3A%2F%2Fwww.lifewithheidi.com%2F&ul=en-us&de=UTF-8&dt=Homepage%20%E2%8B%86%20Life%20With%20Heidi&sd=24-bit&sr=360x640&vp=1440x2560&je=0&_u=IEBAAUABAAAAAC~&jid=&gjid=&cid=1269297094.1616520627&tid=UA-30348332-1&_gid=1837988999.1616520627&gtm=2ou3h0&z=299114608
h2
2236.6379997693
2240.1519999839
602
35
200
image/gif
Image
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j88&tid=UA-30348332-1&cid=1269297094.1616520627&jid=1422332058&gjid=1918557881&_gid=1837988999.1616520627&_u=IEBAAUAAAAAAAC~&z=1497530111
h2
2237.964999862
2241.2000000477
697
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1761.95
11.127
1774.315
7.329
1909.659
23.007
1932.679
83.521
2017.223
5.705
2033.05
5.773
2043.233
45.221
2104.057
22.34
2126.457
9.007
2135.474
16.445
2151.961
5.45
2165.488
9.379
2175.961
16.795
2194.563
34.528
2230.094
28.927
2270.686
47.317
2321.322
5.248
2326.781
44.527
2375.087
7.123
2397.403
17.551
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lifewithheidi.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Lifewithheidi.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lifewithheidi.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 3 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lifewithheidi.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.lifewithheidi.com/wp-content/plugins/genesis-responsive-slider/assets/js/jquery.flexslider.js?ver=1.0.1
5785
2830
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lifewithheidi.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://lifewithheidi.com/wp-content/themes/restored316-farmhouse/config/import/images/large-bg.jpg
0

Diagnostics

Uses efficient cache policy on static assets — 1 resource found
Lifewithheidi.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
19609
Avoids an excessive DOM size — 713 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
713
Maximum DOM Depth
img
20
Maximum Child Elements
14
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Lifewithheidi.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.lifewithheidi.com/
1300.804
11.04
6.344
Unattributable
466.568
4.028
0.864
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
185.748
106.884
72.168
https://www.google-analytics.com/analytics.js
127.656
111.46
5.688
https://www.lifewithheidi.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
65.888
54.348
7.32
Keep request counts low and transfer sizes small — 65 requests • 11,514 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
65
11790216
Image
13
11103755
Font
14
375747
Script
17
163221
Stylesheet
16
121429
Document
1
23910
Other
4
2154
Media
0
0
Third-party
16
191623
Minimize third-party usage — Third-party code blocked the main thread for 50 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)
22040
51.276
128372
0
40514
0
697
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.027190839336325
0.015205080529551
0.010399115021573
0.010122910107321
0.0019334343997612
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 9 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.lifewithheidi.com/
2096
167
https://www.lifewithheidi.com/
664
138
https://www.lifewithheidi.com/
802
95
https://www.lifewithheidi.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
5640
92
https://www.lifewithheidi.com/
2263
90
https://www.lifewithheidi.com/
897
89
Unattributable
986
70
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
3512
66
https://www.google-analytics.com/analytics.js
4546
58
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

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

Metrics

First Contentful Paint — 3.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 5.6 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 5.0 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 4.4 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 3.8 s
The time taken for the primary content of the page to be rendered.

Opportunities

Remove unused CSS — Potential savings of 48 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lifewithheidi.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.lifewithheidi.com/wp-content/litespeed/cssjs/bdadc.css?8c3b0
35464
35214
https://fonts.googleapis.com/css?family=Nanum+Myeongjo:wght@400;800
13959
13959
Remove unused JavaScript — Potential savings of 52 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-30348332-1
40514
30001
https://www.lifewithheidi.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
30654
22969

Diagnostics

Minimize main-thread work — 2.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Rendering
605.804
Style & Layout
579.276
Other
578.564
Script Evaluation
308.732
Script Parsing & Compilation
111.472
Parse HTML & CSS
100.544

Metrics

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

Opportunities

Properly size images — Potential savings of 7,765 KiB
Images can slow down the page's load time. Lifewithheidi.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Frugal-Living.png
6014463
4788401
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Recipes.png
2508157
1996864
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Travel.jpg
1924254
1082342
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Create-DIY-scaled.jpg
258136
84033
Efficiently encode images — Potential savings of 1,344 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Travel.jpg
1924254
1376587
Serve images in next-gen formats — Potential savings of 7,856 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Frugal-Living.png
6014463
4814463
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Travel.jpg
1924254
1699566
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Recipes.png
2508157
1308157
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Create-DIY-scaled.jpg
258136
157054
https://www.lifewithheidi.com/wp-content/uploads/2021/03/7-Benefits-Of-Buying-A-New-Build-Property-.jpg
79290
35518
https://www.lifewithheidi.com/wp-content/uploads/2021/03/Planning-A-Budget-Bathroom-Makeover.jpg
68689
30191
Reduce initial server response time — Root document took 680 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.lifewithheidi.com/
676.506
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Lifewithheidi.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lifewithheidi.com/
630
https://lifewithheidi.com/
480
https://www.lifewithheidi.com/
0

Diagnostics

Avoid enormous network payloads — Total size was 11,514 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Frugal-Living.png
6014781
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Recipes.png
2508475
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Travel.jpg
1924573
https://www.lifewithheidi.com/wp-content/uploads/2021/01/Create-DIY-scaled.jpg
258454
https://lifewithheidi.com/wp-content/themes/restored316-farmhouse/config/import/images/large-bg.jpg
198959
https://www.lifewithheidi.com/wp-content/uploads/2021/03/7-Benefits-Of-Buying-A-New-Build-Property-.jpg
79607
https://www.lifewithheidi.com/wp-content/uploads/2021/03/Planning-A-Budget-Bathroom-Makeover.jpg
69006
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/MonologueScript-Regular.woff2
62889
https://www.lifewithheidi.com/wp-content/uploads/2019/12/heidi.jpg
41497
https://www.lifewithheidi.com/wp-content/themes/restored316-farmhouse/assets/fonts/FreightDispProBook-Regular.woff2
41317
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.119.woff2
4.1290000081062
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.117.woff2
3.772999625653
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.118.woff2
3.6780000664294
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.99.woff2
2.743000164628
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.114.woff2
3.3220001496375
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.115.woff2
14.76400019601
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.109.woff2
3.4050000831485
https://fonts.gstatic.com/s/nanummyeongjo/v15/9Btx3DZF0dXLMZlywRbVRNhxy1LueHI8j7a277xGHHfvDTP5cQDfPh1ShL-7.116.woff2
3.6079999990761

Other

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

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Lifewithheidi.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that lifewithheidi.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.

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
WebFont Loader
WordPress
5.7
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.
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://lifewithheidi.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.lifewithheidi.com/wp-content/uploads/2019/12/heidi.jpg
478 x 478
600 x 600
956 x 956
https://www.lifewithheidi.com/wp-content/uploads/2021/01/cropped-LWH-1.png
375 x 234
500 x 312
750 x 468

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
SyntaxError: Unexpected identifier
86

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for lifewithheidi.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 lifewithheidi.com on mobile screens.
Document uses legible font sizes — 98.37% 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
a.button, button, input[type=button], input[type=reset], input[type=submit], .entry-content a.button, .site-container div.wpforms-container-full .wpforms-form input[type=submit], .site-container div.wpforms-container-full .wpforms-form button[type=submit]
0.60%
11px
.genesis-nav-menu a
0.31%
11px
.site-container .wp-block-button .wp-block-button__link
0.23%
11px
.is-style-capital-text, .editor-styles-wrapper .is-style-capital-text
0.19%
11px
h3
0.15%
11px
.site-footer
0.14%
11px
body
0.02%
10px
98.37%
≥ 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.
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.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Manual Checks

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

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 lifewithheidi.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: 162.248.188.100
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
AOD Hosting
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Save More Spend Less with Heidi
Country: US
City:
State: Missouri
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 104.70.50.181
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 3/5 (0 reviews)
WOT Trustworthiness: 61/100
WOT Child Safety: 94/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: lifewithheidi.com
Issued By: cPanel, Inc. Certification Authority
Valid From: 19th March, 2021
Valid To: 17th June, 2021
Subject: CN = lifewithheidi.com
Hash: d82300e5
Issuer: CN = cPanel, Inc. Certification Authority
O = cPanel, Inc.
S = US
Version: 2
Serial Number: 0xAB188564C7A09DC6092E921D07A2BA95
Serial Number (Hex): AB188564C7A09DC6092E921D07A2BA95
Valid From: 19th March, 2024
Valid To: 17th June, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:7E:03:5A:65:41:6B:A7:7E:0A:E1:B8:9D:08:EA:1D:8E:1D:6A:C7:65
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.comodoca.com/cPanelIncCertificationAuthority.crl

Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.52
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://crt.comodoca.com/cPanelIncCertificationAuthority.crt
OCSP - URI:http://ocsp.comodoca.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Mar 19 03:09:43.095 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:0E:03:AE:70:CB:A5:D1:CA:DD:06:3D:A5:
EC:80:DA:F0:F9:10:A1:A3:00:11:8D:05:06:50:43:B4:
45:EE:A0:E3:02:21:00:FA:87:44:CC:AF:D6:38:B1:77:
B0:09:F5:9C:0E:89:E5:D8:7D:90:1B:8A:27:35:ED:1E:
46:93:CC:01:C5:B9:8E
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Mar 19 03:09:43.011 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:37:71:DE:66:5A:68:22:0E:26:A5:7B:1B:
C3:22:9C:AF:E1:E6:3E:56:C9:C2:13:68:56:4C:FB:24:
41:6D:7A:40:02:20:1F:17:54:52:52:F5:D9:68:4D:D9:
ED:22:2E:A6:EA:A8:80:CF:40:6C:50:52:CF:3B:92:92:
89:AD:76:44:DD:E7
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:mail.lifewithheidi.com
DNS:www.lifewithheidi.com
DNS:lifewithheidi.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
lifewithheidi.com. 162.248.188.100 IN 3599

NS Records

Host Nameserver Class TTL
lifewithheidi.com. ns1.liquidweb.com. IN 3599
lifewithheidi.com. ns.liquidweb.com. IN 3599

MX Records

Priority Host Server Class TTL
10 lifewithheidi.com. mx.zoho.com. IN 299
20 lifewithheidi.com. mx2.zoho.com. IN 299
50 lifewithheidi.com. mx3.zoho.com. IN 299

SOA Records

Domain Name Primary NS Responsible Email TTL
lifewithheidi.com. ns.liquidweb.com. admin.liquidweb.com. 3599

TXT Records

Host Value Class TTL
lifewithheidi.com. v=spf1 IN 299

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Date: 23rd March, 2021
Server: LiteSpeed
Connection: Keep-Alive
Link: <https://www.lifewithheidi.com/>; rel=shortlink
Vary: User-Agent
Alt-Svc: quic=":443"; ma=2592000; v="43,46", h3-Q043=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-25=":443"; ma=2592000, h3-27=":443"; ma=2592000

Whois Lookup

Created: 9th November, 2015
Changed: 11th October, 2020
Expires: 9th November, 2021
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns.liquidweb.com
ns1.liquidweb.com
Owner Organization: Save More Spend Less with Heidi
Owner State: Missouri
Owner Country: US
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=lifewithheidi.com
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=lifewithheidi.com
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=lifewithheidi.com
Full Whois: Domain Name: lifewithheidi.com
Registry Domain ID: 1977585401_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2020-10-11T21:20:15Z
Creation Date: 2015-11-09T12:12:05Z
Registrar Registration Expiration Date: 2021-11-09T12:12:05Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registrant Organization: Save More Spend Less with Heidi
Registrant State/Province: Missouri
Registrant Country: US
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=lifewithheidi.com
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=lifewithheidi.com
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=lifewithheidi.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-03-23T17:28:40Z <<<

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

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

Nameservers

Name IP Address
ns.liquidweb.com 69.16.222.254
ns1.liquidweb.com 69.16.223.254
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$1,023 USD 2/5
$5,665 USD 2/5
$1,029 USD 1/5
$4,456 USD 3/5