439 ms in total
14 ms
347 ms
78 ms
Welcome to discursive.com homepage info - get ready to check Discursive best content for United States right away, or after learning these important things about discursive.com
I am a software engineer, Manager, and architect in Seattle, WA. Read my articles.
Visit discursive.comWe analyzed Discursive.com page load time and found that the first response time was 14 ms and then it took 425 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.
discursive.com performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value6.5 s
9/100
25%
Value3.4 s
90/100
10%
Value1,010 ms
27/100
30%
Value0
100/100
15%
Value6.6 s
57/100
10%
14 ms
81 ms
36 ms
72 ms
53 ms
Our browser made a total of 15 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original Discursive.com, 67% (10 requests) were made to About.me and 7% (1 request) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (135 ms) relates to the external source About.me.
Page size can be reduced by 90.9 kB (77%)
118.3 kB
27.4 kB
In fact, the total size of Discursive.com main page is 118.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. HTML takes 114.6 kB which makes up the majority of the site volume.
Potential reduce by 90.9 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 90.9 kB or 79% of the original size.
Potential reduce by 0 B
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. Discursive images are well optimized though.
Potential reduce by 0 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.
We found no issues to fix!
5
5
The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discursive. According to our analytics all requests are already optimized.
discursive.com
14 ms
discursive.com
81 ms
geu7rrs.css
36 ms
3a8ec81a.bundle.js
72 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
53 ms
p.css
31 ms
tobrien_1672418250_984.jpg
135 ms
proxima_nova_bold-punc.woff
11 ms
proxima_nova_bold-latin-a.woff
12 ms
proximanova-bold-webfont.woff
21 ms
proxima_nova_reg-punc.woff
30 ms
proxima_nova_reg-latin-a.woff
29 ms
proximanova-regular-webfont.woff
28 ms
proximanova-light-webfont.woff
29 ms
aboutme-glyphs.woff
22 ms
discursive.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.
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
discursive.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
Browser errors were logged to the console
Page has valid source maps
discursive.com SEO score
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
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discursive.com 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 Discursive.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.
discursive.com
Open Graph data is detected on the main page of Discursive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: