2 sec in total
107 ms
1.8 sec
68 ms
Visit lindseypogue.com now to see the best up-to-date Lindsey Pogue content and also check out these interesting facts you probably never knew about lindseypogue.com
Whether you're a avid romance reader or prefer adventures in post-apocalyptic worlds, Author Lindsey Pogue writes a little bit of everything. Here you will find small town romance, sand ravaged worlds...
Visit lindseypogue.comWe analyzed Lindseypogue.com page load time and found that the first response time was 107 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
lindseypogue.com performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value9.4 s
0/100
25%
Value8.5 s
18/100
10%
Value730 ms
41/100
30%
Value0.133
81/100
15%
Value15.0 s
7/100
10%
107 ms
58 ms
102 ms
567 ms
73 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lindseypogue.com, 47% (28 requests) were made to Static.wixstatic.com and 27% (16 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 909.8 kB (60%)
1.5 MB
596.1 kB
In fact, the total size of Lindseypogue.com main page is 1.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.
Potential reduce by 810.7 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 810.7 kB or 80% of the original size.
Potential reduce by 37.2 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Lindsey Pogue needs image optimization as it can save up to 37.2 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 61.9 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 61.9 kB or 21% of the original size.
Number of requests can be reduced by 10 (26%)
38
28
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lindsey Pogue. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.lindseypogue.com
107 ms
minified.js
58 ms
focus-within-polyfill.js
102 ms
polyfill.min.js
567 ms
thunderbolt-commons.1e70fbb2.bundle.min.js
73 ms
main.42e492e1.bundle.min.js
74 ms
lodash.min.js
75 ms
react.production.min.js
77 ms
react-dom.production.min.js
79 ms
siteTags.bundle.min.js
75 ms
wix-perf-measure.umd.min.js
76 ms
Fixed%20branding%20.png
276 ms
232035_b07219b9355241bca0daf891525fa3fe~mv2.jpeg
267 ms
232035_76a54709887d4b8e8b4144b76fff75a0~mv2.jpeg
378 ms
232035_7c96b04563854fc18e4b12ad83982a34~mv2.jpeg
379 ms
232035_b0b2b29e28ee4197beb2d06d541fdad0~mv2.jpeg
401 ms
232035_19417594bdc645f6ac1dc6ef31adcc5d~mv2.png
380 ms
Cursed%20eReader.png
378 ms
orange.png
418 ms
232035_a8a8b701fb3a43c38f4e3f27747244a3~mv2.png
619 ms
Author%20Name%20Banner.png
524 ms
ava.png
530 ms
TDW%20Nice%20eBook.png
592 ms
232035_f4c1b985738b4aa1a7764968a4138b54~mv2.png
590 ms
232035_727663b2cc9645ba9f6ae8e4e1b126af~mv2.png
647 ms
Author%20Name%20Banner%20(1).png
727 ms
232035_1fc3820740f74cad852e209859f1da38~mv2.png
707 ms
232035_319b7a75a40b446aad0a0b7ccb16fe22~mv2.png
782 ms
232035_de00553302134becb45cb319f3deafaf~mv2.jpg
780 ms
232035_243fdf4a09614ee7bb956423ee9a4d20~mv2.png
730 ms
goodreads%2096x96.png
850 ms
232035_d952860b526d4e7e8e95844666c2abcb~mv2.png
869 ms
BB%2096x96.png
938 ms
copyright-1345865.png
1017 ms
bundle.min.js
105 ms
file.woff
641 ms
file.woff
682 ms
file.woff
709 ms
file.woff
739 ms
opensans-bold-webfont.woff
67 ms
opensans-regular-webfont.woff
68 ms
file.woff
761 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
9 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
8 ms
139 ms
157 ms
154 ms
154 ms
157 ms
141 ms
170 ms
187 ms
180 ms
179 ms
180 ms
195 ms
deprecation-en.v5.html
7 ms
bolt-performance
19 ms
deprecation-style.v5.css
7 ms
right-arrow.svg
7 ms
lindseypogue.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
lindseypogue.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lindseypogue.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lindseypogue.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Lindseypogue.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
lindseypogue.com
Open Graph data is detected on the main page of Lindsey Pogue. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: