6 sec in total
510 ms
5 sec
446 ms
Visit interlude.su now to see the best up-to-date Interlude content for Russia and also check out these interesting facts you probably never knew about interlude.su
Interlude.Su - лучший комплекс серверов Lineage 2 Interlude
Visit interlude.suWe analyzed Interlude.su page load time and found that the first response time was 510 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
interlude.su performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value11.4 s
0/100
25%
Value32.6 s
0/100
10%
Value42,360 ms
0/100
30%
Value0.746
6/100
15%
Value68.3 s
0/100
10%
510 ms
194 ms
159 ms
315 ms
783 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 50% of them (61 requests) were addressed to the original Interlude.su, 15% (19 requests) were made to Um.simpli.fi and 3% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Vk.com.
Page size can be reduced by 176.4 kB (21%)
836.6 kB
660.3 kB
In fact, the total size of Interlude.su main page is 836.6 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. 40% of websites need less resources to load. Images take 579.6 kB which makes up the majority of the site volume.
Potential reduce by 18.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. This page needs HTML code to be minified as it can gain 3.0 kB, which is 12% 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 18.8 kB or 75% of the original size.
Potential reduce by 18.1 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. Interlude images are well optimized though.
Potential reduce by 116.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 116.6 kB or 57% of the original size.
Potential reduce by 22.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. Interlude.su needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 82% of the original size.
Number of requests can be reduced by 40 (41%)
97
57
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Interlude. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
interlude.su
510 ms
interlude.su
194 ms
style.css
159 ms
engine.css
315 ms
jquery.js
783 ms
stressweb.js
320 ms
facebox.css
319 ms
facebox.js
319 ms
langpopup.css
320 ms
langpopup.js
469 ms
conversion.js
17 ms
body_bg.gif
159 ms
wrapper_border.gif
158 ms
header_bg.jpg
785 ms
l2top_bg.jpg
163 ms
l2top.pgif
160 ms
panel_left_bg.jpg
315 ms
vk_icon.gif
165 ms
facebook_icon.gif
311 ms
mail_icon.gif
314 ms
twitter_icon.gif
315 ms
live_icon.gif
316 ms
world_icon.gif
466 ms
panel_right_bg.jpg
627 ms
lang_bg.gif
469 ms
lang_eng.gif
471 ms
lang_ru.gif
471 ms
panel_center_bg.jpg
621 ms
logo.jpg
627 ms
content_bg.jpg
939 ms
footer_bg.jpg
938 ms
info_title_bg.gif
776 ms
info_title.gif
778 ms
info_bg.jpg
781 ms
menu_p.gif
933 ms
title_bg.gif
934 ms
files_title.gif
934 ms
block_bg.gif
937 ms
community_title.gif
1089 ms
t1.gif
1090 ms
t2.gif
1090 ms
stat_title.gif
1091 ms
counter_bg.gif
1093 ms
colored.js
130 ms
hit
262 ms
64 ms
2714.png
3237 ms
video_title_bg.gif
1072 ms
video_title.gif
1225 ms
video_bg.jpg
1225 ms
video_prev.jpg
1227 ms
title_bg_r.gif
1227 ms
watch.js
182 ms
rtrg
3447 ms
30 ms
8 ms
status_title.gif
1105 ms
dpx.js
10 ms
block_bg_r.gif
1097 ms
ico-on.png
1246 ms
forum_title.gif
1246 ms
tpid=1EE70445598CEE561B03413502908EE4
9 ms
p
3 ms
dpx
2 ms
aol
5 ms
mapuser
6 ms
watch.js
434 ms
y_match
4 ms
match_redirect
4 ms
29931
91 ms
hit
132 ms
theme_p.gif
1104 ms
content_top_bg.jpg
1411 ms
t_news.jpg
1100 ms
news_p.jpg
1107 ms
news_icon_01.png
1247 ms
match_redirect
4 ms
tpid=CE29559E598CEE56D46FD84B02FB7350
4 ms
lr
8 ms
lr.gif
5 ms
match_redirect
4 ms
sync
12 ms
46 ms
match_redirect
4 ms
CE29559E598CEE56D46FD84B02FB7350
47 ms
pict_border.png
1100 ms
pict_01.jpg
1097 ms
popup-bg.png
1096 ms
popup-lang-ru.png
1099 ms
66 ms
tc.js
6 ms
p
48 ms
exelate
3 ms
13 ms
v2
45 ms
29 ms
19 ms
dpx
3 ms
spotx_match
5 ms
popup-lang-en.png
1099 ms
xrefid.xgi
6 ms
ca.png
170 ms
advert.gif
85 ms
52154.gif
6 ms
fb_match
4 ms
u.php
76 ms
an
4 ms
lj_match
5 ms
merge
5 ms
cw_match
4 ms
rtset
19 ms
rb_match
4 ms
1
86 ms
tap.php
9 ms
ox_match
5 ms
sd
26 ms
pm_match
4 ms
Pug
47 ms
pixel
21 ms
g_match
4 ms
match_redirect
4 ms
pixel
37 ms
aa_px
3 ms
interlude.su 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
interlude.su 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
Missing source maps for large first-party JavaScript
interlude.su 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Interlude.su 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Interlude.su 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.
interlude.su
Open Graph description is not detected on the main page of Interlude. 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: