5.1 sec in total
559 ms
3.7 sec
882 ms
Click here to check amazing Fortis Spb content for Russia. Otherwise, check out these important facts you probably never knew about fortis-spb.ru
Наша компания предлагает бетонные заборы. Блоки для столбов и заборов. Всегда в наличии крышки на столбы и парапеты. Качественные заборы от производителя - ООО Фортис.
Visit fortis-spb.ruWe analyzed Fortis-spb.ru page load time and found that the first response time was 559 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fortis-spb.ru performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value8.8 s
1/100
25%
Value6.2 s
44/100
10%
Value130 ms
96/100
30%
Value0.043
99/100
15%
Value10.6 s
23/100
10%
559 ms
755 ms
42 ms
142 ms
290 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 85% of them (67 requests) were addressed to the original Fortis-spb.ru, 11% (9 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fortis-spb.ru.
Page size can be reduced by 56.8 kB (2%)
2.4 MB
2.3 MB
In fact, the total size of Fortis-spb.ru main page is 2.4 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 36.5 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 8.6 kB, which is 19% 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 36.5 kB or 80% of the original size.
Potential reduce by 1.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. Fortis Spb images are well optimized though.
Potential reduce by 15.4 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 3.9 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. Fortis-spb.ru needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 15% of the original size.
Number of requests can be reduced by 24 (36%)
67
43
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fortis Spb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
fortis-spb.ru
559 ms
fortis-spb.ru
755 ms
css2
42 ms
bootstrap.css
142 ms
style.css
290 ms
default.css
409 ms
jquery.jgrowl.min.css
411 ms
default.css
414 ms
jquery-3.2.1.min.js
598 ms
jquery.fancybox.js
600 ms
slick.min.js
595 ms
jquery.touchswipe.min.js
596 ms
easylistsplitter.js
597 ms
jquery.inputmask.js
734 ms
scripts.js
597 ms
default.js
686 ms
jquery.jgrowl.min.js
690 ms
message_settings.js
737 ms
custom.js
738 ms
style.css
299 ms
image01.png
386 ms
burger-icon.svg
387 ms
03_1912x620_bea.jpg
1060 ms
sl01_1912x620_bea.jpg
824 ms
2e3zdxyi-output-0_555x450_1f6.jpeg
542 ms
34118f72-0741-40ae-9e7c-4209587bdaf2_555x450_88a.jpg
546 ms
pj32fxyq-output-0_555x450_1f6.jpeg
779 ms
f0bd56a6-7715-4398-a410-837dc5e29a8c_555x450_88a.jpg
789 ms
m3svgiuk-output-0_555x450_1f6.jpeg
820 ms
img-7352_555x450_88a.jpg
687 ms
qp1dmcks-output-0_555x450_1f6.jpeg
829 ms
img-7390_555x450_88a.jpg
1048 ms
ydc4qoy1-output-0_555x450_1f6.jpeg
1061 ms
img-7782_555x450_88a.jpg
960 ms
t05_310x270_dc7.jpg
963 ms
t02_310x270_dc7.jpg
966 ms
t01_310x270_dc7.jpg
1100 ms
t03_310x270_dc7.jpg
1103 ms
t04_310x270_dc7.jpg
1106 ms
t08_310x270_dc7.jpg
1182 ms
t06_310x270_dc7.jpg
1194 ms
t07_310x270_dc7.jpg
1196 ms
kapitel-290h290-390h390-h80-sery1_310x270_160.png
1237 ms
t09_310x270_dc7.jpg
1098 ms
index001_528x0_876.jpg
1100 ms
list-check.svg
1175 ms
features1.png
1184 ms
features2.png
1184 ms
features3.png
1228 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
21 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
55 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
120 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
71 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
120 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
69 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
68 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
121 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
121 ms
morelink-arrow.svg
1212 ms
-15.jpg
1147 ms
-5.jpg
1170 ms
.jpg
1180 ms
-2.jpg
1176 ms
-2.jpg
1222 ms
tag.js
954 ms
-19.jpg
1188 ms
news01_305x190_6af.jpg
1144 ms
207a597d856ff6af3387721afd6be968308b0318.jpg
1198 ms
footer-features1.svg
1076 ms
footer-features2.svg
1071 ms
footer-features3.svg
973 ms
footer-features4.svg
893 ms
location-icon.svg
880 ms
feedbackbutton.svg
909 ms
telegram.svg
930 ms
whatsapp.svg
926 ms
messagers-btns-phone.svg
839 ms
style.css
849 ms
advert.gif
564 ms
fortis-spb.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
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.
fortis-spb.ru 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fortis-spb.ru 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
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fortis-spb.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Fortis-spb.ru 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.
fortis-spb.ru
Open Graph description is not detected on the main page of Fortis Spb. 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: