6.1 sec in total
2.4 sec
3.1 sec
571 ms
Welcome to narrative.ly homepage info - get ready to check Narrative best content for United States right away, or after learning these important things about narrative.ly
Discover extraordinary true stories celebrating the diversity of humanity. Click to read Narratively, a Substack publication with tens of thousands of subscribers.
Visit narrative.lyWe analyzed Narrative.ly page load time and found that the first response time was 2.4 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
narrative.ly performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value24.4 s
0/100
25%
Value17.2 s
0/100
10%
Value8,470 ms
0/100
30%
Value0.174
69/100
15%
Value25.1 s
0/100
10%
2351 ms
53 ms
61 ms
23 ms
96 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 16% of them (5 requests) were addressed to the original Narrative.ly, 48% (15 requests) were made to S3.amazonaws.com and 10% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Narrative.ly.
Page size can be reduced by 283.1 kB (15%)
1.9 MB
1.6 MB
In fact, the total size of Narrative.ly main page is 1.9 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 19.0 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 19.0 kB or 70% of the original size.
Potential reduce by 263.8 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, Narrative needs image optimization as it can save up to 263.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 289 B
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. Narrative.ly needs all CSS files to be minified and compressed as it can save up to 289 B or 53% of the original size.
Number of requests can be reduced by 6 (21%)
29
23
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Narrative. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
narrative.ly
2351 ms
screen.css
53 ms
app.js
61 ms
css
23 ms
ga.js
96 ms
00dbRhySRSqlyTVa3w5K_header3.png
92 ms
sponsor_message.png
38 ms
FC29BX7lQ3ebBl6pS3co_header-1.jpg
38 ms
d3NE5K9QJOnLBK5s9ZSg_Narratively-MercedesFromHeaven-V2.jpg
96 ms
4fiv8dPvQDC0KcVTrnYD_header-1.jpg
67 ms
syoEMiFSpuoSV6m4Hhvl_header-1.jpg
58 ms
NVcETTONQ0KrcAv8lnQg_smaller%20header.jpg
108 ms
4pLHCooSRSF59U608ncB_trade%20building_final.jpg
63 ms
a8Y4XdA3RuSt63JYKCpq_Narratively_Color_Header.jpg
59 ms
oJXNuVaUTPSoQhOte8J7_HEADERElliotRoss_ReckoningDays_14.jpg
83 ms
kzI4FbKyQRGrOHDUo1WI_header-1.jpg
76 ms
v1JNNumQ1enBxjuH5gdQ_SxnY0V3Ske5U2BXnccAl_iDolls-1.jpg
154 ms
hG422pe4ScGOCGWGvoIz_00HEADERBlanchard%2C%20Kid%2C%20Cape%20Town%20%286%29.JPG
157 ms
qOhyAs5pRWTVb5f1g8Hg_KimSalt_ModernLove_header.jpg
107 ms
ATkgt7bcTrS3kmFf2yuN_header-2.jpg
126 ms
Eh00gEApSPWoHRisuGM1_homeless-header.jpg
153 ms
logo.png
32 ms
4WwBI2xBQBEAAA=
7 ms
__utm.gif
12 ms
all.js
505 ms
platform.js
88 ms
widgets.js
52 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
3 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
18 ms
info.json
82 ms
jot
93 ms
narrative.ly accessibility score
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-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
narrative.ly best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
narrative.ly 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Narrative.ly can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Narrative.ly 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.
narrative.ly
Open Graph description is not detected on the main page of Narrative. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: