1.7 sec in total
275 ms
1.2 sec
238 ms
Click here to check amazing Lon Story content. Otherwise, check out these important facts you probably never knew about lonstory.com
In A Lon Beginning, a child searches for their mother on a distant planet, and discovers answers to questions they never knew to ask.
Visit lonstory.comWe analyzed Lonstory.com page load time and found that the first response time was 275 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
lonstory.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value11.1 s
0/100
25%
Value9.2 s
13/100
10%
Value430 ms
65/100
30%
Value1.145
1/100
15%
Value17.2 s
4/100
10%
275 ms
16 ms
126 ms
204 ms
128 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 57% of them (42 requests) were addressed to the original Lonstory.com, 8% (6 requests) were made to I0.wp.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (553 ms) belongs to the original domain Lonstory.com.
Page size can be reduced by 242.1 kB (3%)
8.0 MB
7.8 MB
In fact, the total size of Lonstory.com main page is 8.0 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. 70% of websites need less resources to load. Images take 7.7 MB which makes up the majority of the site volume.
Potential reduce by 67.8 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 67.8 kB or 75% of the original size.
Potential reduce by 134.5 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. Lon Story images are well optimized though.
Potential reduce by 13.7 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 13.7 kB or 13% of the original size.
Potential reduce by 26.1 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Lonstory.com needs all CSS files to be minified and compressed as it can save up to 26.1 kB or 29% of the original size.
Number of requests can be reduced by 43 (63%)
68
25
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lon Story. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
lonstory.com
275 ms
js
16 ms
gtranslate-style24.css
126 ms
style.min.css
204 ms
mediaelementplayer-legacy.min.css
128 ms
wp-mediaelement.min.css
135 ms
front-flex.min.css
136 ms
style.css
135 ms
style.css
196 ms
font-awesome.css
207 ms
social-media-widget.css
211 ms
mobilenav.css
211 ms
subscriptions.css
209 ms
style.css
266 ms
default.min.css
264 ms
sharing.css
267 ms
social-logos.min.css
276 ms
jquery.min.js
336 ms
jquery-migrate.min.js
280 ms
frontend-gtag.min.js
335 ms
jquery.flexslider.min.js
348 ms
jquery.touchSwipe.min.js
334 ms
jquery.theme-main.min.js
350 ms
mobilenav.min.js
351 ms
js
68 ms
share-button.js
25 ms
so-css-vantage.css
376 ms
nivo-slider.css
374 ms
public.css
375 ms
public.css
374 ms
default.css
407 ms
sow-image-default-d6014b76747a-4.css
375 ms
queuehandler.min.js
465 ms
e-202441.js
37 ms
jquery.nivo.slider.pack.js
466 ms
sharing.min.js
465 ms
element.js
42 ms
css
21 ms
smalllogo-e1512622881412.png
70 ms
lonsliderfinal.jpg
430 ms
chapter1sliderf.jpg
481 ms
solbabys.jpg
476 ms
amaslider-1.jpg
427 ms
elleamaslider2-1.jpg
433 ms
elleamaslider.jpg
490 ms
avalonbabylonslider-1.jpg
553 ms
alonbeginningcoversmall.jpg
57 ms
craigprobe.jpg
55 ms
kelfingerbreak.jpg
106 ms
downloads_wordmark_white_on_coral@2x.png
108 ms
become_a_patron_button@2x-300x71.png
108 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
44 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMQQ.woff
92 ms
vantage-icons.woff
454 ms
fontawesome-webfont.woff
462 ms
widgets.js
52 ms
sdk.js
60 ms
master.html
58 ms
button
84 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
95 ms
sdk.js
14 ms
white.png
357 ms
favicon.ico
105 ms
rlt-proxy.js
51 ms
78 ms
index.build.css
18 ms
index.build.js
22 ms
settings
157 ms
beacon.js
51 ms
impixu
50 ms
flat-t-button-white.svg
20 ms
button.856debeac157d9669cf51e73a08fbc93.js
2 ms
embeds
39 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.en.html
10 ms
lonstory.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
lonstory.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lonstory.com SEO score
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 Lonstory.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 Lonstory.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.
lonstory.com
Open Graph data is detected on the main page of Lon Story. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: