3.5 sec in total
248 ms
3 sec
283 ms
Welcome to intently.com homepage info - get ready to check Intently best content for Switzerland right away, or after learning these important things about intently.com
replace online ads with inspiration
Visit intently.comWe analyzed Intently.com page load time and found that the first response time was 248 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
intently.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value3.7 s
59/100
25%
Value3.0 s
94/100
10%
Value250 ms
85/100
30%
Value0.099
90/100
15%
Value3.9 s
88/100
10%
248 ms
313 ms
900 ms
58 ms
533 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 77% of them (76 requests) were addressed to the original Intently.com, 6% (6 requests) were made to Api.intently.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (900 ms) belongs to the original domain Intently.com.
Page size can be reduced by 197.4 kB (66%)
298.5 kB
101.0 kB
In fact, the total size of Intently.com main page is 298.5 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. 45% of websites need less resources to load. HTML takes 142.6 kB which makes up the majority of the site volume.
Potential reduce by 109.6 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 109.6 kB or 77% of the original size.
Potential reduce by 2.0 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. Intently images are well optimized though.
Potential reduce by 84.0 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 84.0 kB or 69% of the original size.
Potential reduce by 1.8 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. Intently.com needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 77% of the original size.
Number of requests can be reduced by 61 (75%)
81
20
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intently. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
intently.com
248 ms
intently.com
313 ms
www.intently.com
900 ms
css
58 ms
bootstrap.min.css
533 ms
font-awesome.min.css
314 ms
styles.css
427 ms
modernizr.js
478 ms
URI.min.js
464 ms
URI.fragmentURI.js
394 ms
jquery.min.js
227 ms
jquery-ui.min.js
130 ms
bootstrap.min.js
226 ms
autosize.js
145 ms
velocity.min.js
287 ms
jquery.waitforimages.min.js
68 ms
skrollr.min.js
69 ms
lib.jquery.browser.js
268 ms
lib.jquery.fileupload.js
306 ms
lib.jquery.finaltilesgallery.js
275 ms
lib.jquery.nicescroll.min.js
353 ms
lib.selectize.min.js
281 ms
lib.dropzone.js
391 ms
lib.cookies.min.js
318 ms
lib.bfp.min.js
374 ms
lib.move.js
378 ms
masonry.pkgd.js
71 ms
lib.imagesloaded.js
384 ms
lib.underscore.min.js
401 ms
lib.backbone.min.js
429 ms
app.config.js
471 ms
app.router.js
468 ms
app.plugins.fetch.js
463 ms
app.plugins.form.js
494 ms
app.plugins.extension.js
492 ms
app.plugins.ga.js
505 ms
app.plugins.msg.js
543 ms
app.models.intention.js
560 ms
app.models.notifications.js
561 ms
app.models.user.js
547 ms
app.models.visionboard.js
576 ms
app.models.goal.js
579 ms
app.collections.base.js
621 ms
app.collections.cluster.js
619 ms
app.collections.notifications.js
648 ms
app.views._base.js
637 ms
app.views.base.js
608 ms
app.views.bind.js
569 ms
app.views.connections.js
592 ms
app.views.dashboard.js
570 ms
383d20b33dbbc97d04c08fdf900f7a51_557921aab20679.06480282.png
64 ms
app.views.goals.js
533 ms
app.views.home.js
493 ms
app.views.intention.js
480 ms
app.views.invite.js
494 ms
app.views.members.js
501 ms
app.views.newvisionboard.js
515 ms
app.views.newvisionboardimages.js
527 ms
app.views.notifications.js
538 ms
app.views.overlay.js
533 ms
app.views.onboard.js
501 ms
app.views.search.js
476 ms
app.views.searchbar.js
494 ms
app.views.settings.js
529 ms
app.views.sidebar.js
542 ms
app.views.visionboard.js
519 ms
gray-texture-repeat-80.png
602 ms
%7B%7B=%20obj.intention.src%20%7D%7D
571 ms
%7B%7B=%20obj.avatar_src%20%7D%7D
568 ms
%7B%7B=%20model.src%20%7D%7D
553 ms
%7B%7B=%20obj.cdnFileName%20%7D%7D
553 ms
%7B%7B=%20obj.coverFileNames.split(',')[0]%20%7D%7D
561 ms
analytics.js
60 ms
%7B%7B=%20obj.src%20%7D%7D
548 ms
loading.gif
511 ms
collect
27 ms
subscribed
407 ms
subscribed
454 ms
owned
487 ms
500
508 ms
collect
72 ms
beta
540 ms
config
455 ms
intently-logo-top.png
98 ms
www.intently.com
319 ms
www.intently.com
505 ms
www.intently.com
414 ms
www.intently.com
330 ms
ZvcMqxEwPfh2qDWBPxn6ngV_pQ1T3xN3K1c3sB361us.ttf
67 ms
RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf
115 ms
ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf
128 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
146 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
140 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
142 ms
fontawesome-webfont.woff
255 ms
www.intently.com
346 ms
www.intently.com
487 ms
collect
18 ms
cfdbb629adbcfdda0559209ecf43e89b_56a1241f052224.08258724.jpg
19 ms
intently.com accessibility score
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
intently.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
intently.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intently.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Intently.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.
intently.com
Open Graph data is detected on the main page of Intently. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: