4.2 sec in total
297 ms
3.8 sec
123 ms
Visit 12wave.com now to see the best up-to-date 12Wave content for Russia and also check out these interesting facts you probably never knew about 12wave.com
We specialize in creating unusual and interesting websites which are designed using the latest web technology, varied animation and colorful effects
Visit 12wave.comWe analyzed 12wave.com page load time and found that the first response time was 297 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
12wave.com performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value57.3 s
0/100
25%
Value36.6 s
0/100
10%
Value480 ms
60/100
30%
Value1.012
2/100
15%
Value31.4 s
0/100
10%
297 ms
27 ms
41 ms
88 ms
529 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 93% of them (141 requests) were addressed to the original 12wave.com, 3% (4 requests) were made to Mc.yandex.ru and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain 12wave.com.
Page size can be reduced by 392.5 kB (3%)
11.7 MB
11.3 MB
In fact, the total size of 12wave.com main page is 11.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 11.2 MB which makes up the majority of the site volume.
Potential reduce by 21.2 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.2 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 21.2 kB or 78% 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. 12Wave images are well optimized though.
Potential reduce by 365.7 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 365.7 kB or 68% of the original size.
Potential reduce by 5.6 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. 12wave.com needs all CSS files to be minified and compressed as it can save up to 5.6 kB or 73% of the original size.
Number of requests can be reduced by 9 (6%)
148
139
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 12Wave. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
12wave.com
297 ms
css
27 ms
css
41 ms
style.min.css
88 ms
app.min.js
529 ms
asteroids.png
279 ms
planet1.png
445 ms
ship.png
1219 ms
logo.svg
285 ms
welcome.svg
205 ms
welcome.svg
290 ms
galaxy.png
718 ms
graphics_planet.png
1282 ms
ship.png
840 ms
tent.png
741 ms
spider.png
1058 ms
tablet.png
1076 ms
sketch1.png
830 ms
sketch2.png
917 ms
sketch3.png
1004 ms
prev_image.png
988 ms
next_image.png
1070 ms
lamb.png
1211 ms
st3Author.svg
1139 ms
st3Author.svg
1161 ms
st3Author.svg
1178 ms
st3Author.svg
1225 ms
st3Lamb1.svg
1238 ms
st3Lamb1.svg
1243 ms
st3Lamb1.svg
1264 ms
st3Lamb1.svg
1278 ms
st3Lamb2.svg
1306 ms
st3Lamb2.svg
1314 ms
st3Lamb2.svg
1321 ms
st3Lamb2.svg
1345 ms
st3Lamb3.svg
1367 ms
st3Lamb3.svg
1372 ms
st3Lamb3.svg
1387 ms
st3Lamb3.svg
1394 ms
analytics.js
18 ms
watch.js
176 ms
ship.png
1659 ms
collect
10 ms
collect
62 ms
Zd2E9abXLFGSr9G3YK2MsNbQxvdFQproHqwx84HIuqM.ttf
44 ms
b9QBgL0iMZfDSpmcXcE8nOXJWfeCXjwsU1ch6Jnjz-M.ttf
56 ms
lamb.png
1234 ms
watch.js
595 ms
projector_robot.png
1247 ms
st4Author.svg
1161 ms
st4Author.svg
1189 ms
st4Author.svg
1041 ms
st4Author.svg
869 ms
st4Lamb.svg
823 ms
st4Lamb.svg
829 ms
st4Lamb.svg
731 ms
st4Lamb.svg
756 ms
advert.gif
91 ms
ship_bg.jpg
860 ms
part1_window_right.png
629 ms
web_part1_galaxy_window_right.png
714 ms
1
107 ms
web_part1_stars_window_right.png
587 ms
part1_window_left.png
696 ms
web_part1_stars_window_center.png
615 ms
web_part1_planet2_window_right.png
578 ms
window1.png
755 ms
web_part1_galaxy_window.png
686 ms
stars1.png
600 ms
window2.png
682 ms
stars2.png
624 ms
papers_part1_bg.png
790 ms
papers_part1.png
651 ms
table_part1_center.png
664 ms
table_part1_right.png
687 ms
tech_device.png
767 ms
web_part1_papers_window.png
661 ms
chandelier.png
700 ms
lamb_part1_left.png
696 ms
lamb_part1_right.png
694 ms
st2Author.svg
687 ms
st2Author.svg
721 ms
st2Author.svg
718 ms
st2Author.svg
730 ms
st2Lamb.svg
708 ms
st2Lamb.svg
708 ms
st2Lamb.svg
682 ms
st2Lamb.svg
696 ms
papers.png
745 ms
provod.png
678 ms
lamb1.png
668 ms
lamb2.png
640 ms
lamb3.png
746 ms
lamb4.png
754 ms
st5Author.svg
679 ms
st5Author.svg
646 ms
st5Author.svg
623 ms
st5Author.svg
638 ms
st5Lamb1.svg
652 ms
st5Lamb.svg
666 ms
st5Lamb1.svg
627 ms
st5Lamb.svg
637 ms
st5Lamb2.svg
631 ms
st5Lamb2.svg
582 ms
presentation_screen1.png
649 ms
presentation_screen2.png
645 ms
presentation_screen3.png
652 ms
presentation_button_left.png
534 ms
presentation_button_right.png
577 ms
beam_projection.png
562 ms
projector.png
692 ms
web_lamb_promo.png
595 ms
st6Author.svg
585 ms
st6Author.svg
601 ms
st6Author.svg
591 ms
st6Author.svg
617 ms
st6Lamb1.svg
631 ms
st6Lamb1.svg
602 ms
st6Lamb1.svg
606 ms
st6Lamb1.svg
584 ms
st6Lamb2.svg
596 ms
st6Lamb2.svg
604 ms
st6Lamb2.svg
613 ms
st6Lamb2.svg
583 ms
st6Lamb3.svg
593 ms
st6Lamb3.svg
585 ms
st6Lamb3.svg
602 ms
st6Lamb3.svg
561 ms
contacts_planet.png
635 ms
bg.jpg
550 ms
stars2.png
794 ms
stars.png
536 ms
graphics_bg.jpg
534 ms
stars.png
539 ms
ice_r.png
1060 ms
contacts_bg.jpg
556 ms
logo.png
571 ms
ship_l_bg.jpg
837 ms
button_down.svg
585 ms
button_reload.svg
589 ms
button_up.svg
585 ms
menu_icon.svg
584 ms
st6Lamb4.svg
587 ms
mail_icon.svg
604 ms
menu.svg
648 ms
st5Lamb1.svg
658 ms
st6Lamb4.svg
598 ms
st5Lamb1.svg
605 ms
st6Lamb4.svg
626 ms
web_part1_asteroids_window_left.png
626 ms
web_part1_galaxy2_window_left.png
613 ms
web_part1_planet_window_right.png
637 ms
12wave.com accessibility score
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
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
Image elements do not have [alt] attributes
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.
12wave.com 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
12wave.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 12wave.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 12wave.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.
12wave.com
Open Graph data is detected on the main page of 12Wave. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: