2.5 sec in total
339 ms
1.7 sec
532 ms
Welcome to insayn.net homepage info - get ready to check In Sayn best content right away, or after learning these important things about insayn.net
inSayn -indie video game development based in berlin creating sustainable educational games without loosing the fun part of gaming -contact: info@insayn.net
Visit insayn.netWe analyzed Insayn.net page load time and found that the first response time was 339 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
insayn.net performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value8.4 s
2/100
25%
Value9.7 s
11/100
10%
Value340 ms
74/100
30%
Value0.014
100/100
15%
Value14.2 s
9/100
10%
339 ms
96 ms
191 ms
292 ms
203 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 81% of them (46 requests) were addressed to the original Insayn.net, 5% (3 requests) were made to Db.onlinewebfonts.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (596 ms) belongs to the original domain Insayn.net.
Page size can be reduced by 49.9 kB (13%)
397.5 kB
347.6 kB
In fact, the total size of Insayn.net main page is 397.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. 60% of websites need less resources to load. Javascripts take 317.6 kB which makes up the majority of the site volume.
Potential reduce by 20.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. This page needs HTML code to be minified as it can gain 3.6 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 20.9 kB or 77% 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. In Sayn images are well optimized though.
Potential reduce by 23.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 5.4 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. Insayn.net needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 13% of the original size.
Number of requests can be reduced by 35 (67%)
52
17
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In Sayn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
insayn.net
339 ms
isotope.css
96 ms
jquery.fancybox.css
191 ms
bootstrap.css
292 ms
bootstrap-theme.css
203 ms
style.css
206 ms
default.css
206 ms
css
43 ms
f72b1d468cfaae873bfc1550df0a0f9c
127 ms
ScrollMagic.js
309 ms
TweenMax.min.js
379 ms
animation.gsap.js
296 ms
w3data.js
196 ms
modernizr-2.6.2-respond-1.1.0.min.js
305 ms
jquery.js
406 ms
jquery.easing.1.3.js
383 ms
bootstrap.min.js
391 ms
js
70 ms
jquery.isotope.min.js
408 ms
jquery.nicescroll.min.js
412 ms
jquery.fancybox.pack.js
474 ms
skrollr.min.js
478 ms
jquery.scrollTo-1.4.3.1-min.js
485 ms
jquery.localscroll-1.2.7-min.js
508 ms
jquery.appear.js
508 ms
validate.js
511 ms
main.js
568 ms
w3data.js
14 ms
css
21 ms
font-awesome.css
370 ms
overwrite.css
377 ms
animate.css
407 ms
insayn-image01_edgePreload.js
131 ms
menu2.png
121 ms
w8gdH283Tvk__Lua32TysjIfp8uJ.woff
34 ms
screen01w.png
376 ms
logo02.png
119 ms
Logo%20InSayn%20White.png
200 ms
f72b1d468cfaae873bfc1550df0a0f9c.woff
111 ms
f72b1d468cfaae873bfc1550df0a0f9c.woff
109 ms
screen02.png
596 ms
screen03.png
259 ms
screen04.png
315 ms
screen05.png
372 ms
thankyouinsaynly.png
275 ms
steam.png
338 ms
fb.png
374 ms
twitter.png
395 ms
email.png
433 ms
imprint.png
437 ms
home.png
452 ms
jquery.min.js
8 ms
edge.1.5.0.min.js
364 ms
insayn-image01_edge.js
377 ms
insayn-image01_edgeActions.js
413 ms
jquery.min.js
5 ms
edge.1.5.0.min.js
96 ms
insayn.net 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
Buttons do not have an accessible name
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
insayn.net 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
insayn.net 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Insayn.net 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 Insayn.net 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.
insayn.net
Open Graph description is not detected on the main page of In Sayn. 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: