6.3 sec in total
449 ms
5.4 sec
506 ms
Visit ppk-piter.ru now to see the best up-to-date Ppk Piter content for Russia and also check out these interesting facts you probably never knew about ppk-piter.ru
Расписание электропоездов со всех вокзалов Санкт-Петербурга: Финляндский, Московский, Витебский, Балтийский, Ладожский. Расписание электричек спб.
Visit ppk-piter.ruWe analyzed Ppk-piter.ru page load time and found that the first response time was 449 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ppk-piter.ru performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value6.6 s
8/100
25%
Value5.7 s
51/100
10%
Value280 ms
81/100
30%
Value0
100/100
15%
Value8.8 s
36/100
10%
449 ms
523 ms
109 ms
218 ms
529 ms
Our browser made a total of 200 requests to load all elements on the main page. We found that 98% of them (196 requests) were addressed to the original Ppk-piter.ru, 1% (2 requests) were made to Bitrix.info and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ppk-piter.ru.
Page size can be reduced by 163.0 kB (9%)
1.8 MB
1.6 MB
In fact, the total size of Ppk-piter.ru main page is 1.8 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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 34.7 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 6.5 kB, which is 15% 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 34.7 kB or 80% of the original size.
Potential reduce by 93.7 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. Ppk Piter images are well optimized though.
Potential reduce by 12.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. This website has mostly compressed JavaScripts.
Potential reduce by 21.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. Ppk-piter.ru needs all CSS files to be minified and compressed as it can save up to 21.9 kB or 44% of the original size.
Number of requests can be reduced by 166 (86%)
192
26
The browser has sent 192 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ppk Piter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 155 to 1 for CSS and as a result speed up the page load time.
ppk-piter.ru
449 ms
ppk-piter.ru
523 ms
index.css
109 ms
core.min.css
218 ms
core.min.js
529 ms
jquery.min.js
22 ms
script-min.js
544 ms
datepicker.min.js
40 ms
index.js
339 ms
normalize.css
231 ms
fonts.css
234 ms
swiper-bundle.min.css
335 ms
page.css
339 ms
pages_opened.css
340 ms
link.css
344 ms
list.css
446 ms
fieldset.css
446 ms
input.css
447 ms
button.css
455 ms
button_red.css
523 ms
button_black.css
538 ms
button_back.css
556 ms
button_white.css
554 ms
header.css
555 ms
header_opened.css
566 ms
header_main-page.css
627 ms
header__upper.css
641 ms
header__upper_opened.css
661 ms
header__logo-container.css
662 ms
header__logo.css
666 ms
header__logo_red.css
676 ms
header__logo_white.css
730 ms
header__logo-txt.css
745 ms
header__right-side.css
768 ms
header__right-side_opened.css
770 ms
header__right-side_mobile.css
777 ms
header__special-vision-link.css
785 ms
header__special-vision-txt.css
833 ms
header__special-vision-icon.css
849 ms
header__line.css
876 ms
header__profile-icon.css
876 ms
header__link-btn.css
784 ms
header__link-btn_opened.css
669 ms
header__mobile-btn.css
711 ms
header__mobile-btn_opened.css
724 ms
header__mobile-list.css
653 ms
header__mobile-list_opened.css
652 ms
header__mobile-item.css
663 ms
header__mobile-link.css
667 ms
header__wrapper.css
627 ms
header__wrapper_main-page.css
628 ms
header__wrapper_opened.css
650 ms
header__content.css
653 ms
header__nav.css
665 ms
header__list.css
667 ms
header__list-item.css
627 ms
header__link.css
628 ms
header__form.css
650 ms
header__input.css
651 ms
header__search-btn.css
668 ms
schedule.css
666 ms
schedule__title.css
627 ms
schedule__form.css
627 ms
schedule__fieldset.css
650 ms
schedule__input.css
651 ms
schedule__input_type_date.css
668 ms
schedule__swap-btn.css
666 ms
schedule__search.css
627 ms
schedule__search-btn.css
628 ms
schedule__checkbox-container.css
649 ms
schedule__checkbox-txt.css
650 ms
schedule__checkbox-label.css
667 ms
schedule__checkbox.css
666 ms
schedule__checkmark.css
627 ms
schedule-main.css
627 ms
index-content.css
649 ms
info.css
651 ms
info__block.css
667 ms
info__swiper-slide.css
666 ms
info__swiper-slide-content.css
626 ms
info__swiper-img.css
627 ms
info__swiper-title.css
649 ms
info__swiper-link.css
650 ms
info__swiper-button.css
668 ms
info__swiper-button_next.css
668 ms
info__swiper-button_prev.css
627 ms
info__swiper-pagination.css
627 ms
info__cells.css
649 ms
info__column.css
651 ms
info__list.css
667 ms
info__list_opened.css
655 ms
info__list_type_director.css
640 ms
info__list-item.css
627 ms
info__list-img.css
649 ms
info__cell.css
650 ms
info__cell_opened.css
657 ms
info__cell_type_director.css
658 ms
info__cell_type_economy.css
648 ms
info__cell_type_low-mob.css
628 ms
info__cell_type_privilege.css
650 ms
info__cell_type_scheme.css
651 ms
info__cell_type_work.css
650 ms
info__title.css
660 ms
info__link.css
643 ms
info__link-director.css
638 ms
info__cell-btn.css
649 ms
info__cell-btn_rotate.css
650 ms
news.css
643 ms
news__wrapper.css
653 ms
news__title.css
651 ms
news__card-container.css
645 ms
news__card.css
649 ms
news__img.css
651 ms
news__card-content.css
636 ms
news__card-date.css
645 ms
news__card-brief.css
657 ms
news__card-link.css
651 ms
news__list-item.css
650 ms
news__link.css
651 ms
news__date.css
630 ms
news__txt.css
644 ms
news__list.css
658 ms
news__see-all-link.css
659 ms
tourist.css
650 ms
tourist__title.css
651 ms
tourist__block.css
626 ms
tourist__swiper-slide.css
641 ms
tourist__swiper-slide-content.css
658 ms
tourist__swiper-img.css
665 ms
tourist__swiper-title.css
650 ms
tourist__swiper-link.css
650 ms
tourist__swiper-pagination.css
627 ms
app.css
634 ms
app__wrapper.css
662 ms
app__container.css
667 ms
app__title.css
650 ms
app__txt.css
646 ms
app__buttons.css
631 ms
app__link.css
628 ms
app__img.css
668 ms
footer.css
667 ms
footer__content.css
650 ms
footer__upper.css
643 ms
footer__line.css
636 ms
footer__line_social.css
627 ms
footer__block.css
668 ms
footer__block_type_socials.css
666 ms
footer__blocks_type_contacts.css
642 ms
footer__block_type_nav.css
645 ms
footer__title.css
641 ms
footer__number.css
627 ms
footer__social-link.css
669 ms
footer__socials.css
667 ms
footer__social-txt.css
645 ms
footer__contacts-list.css
646 ms
footer__contacts-list-item.css
627 ms
footer__list.css
668 ms
footer__list-item.css
667 ms
footer__link.css
635 ms
footer__bottom.css
645 ms
footer__bottom-txt.css
644 ms
footer__bottom-img.css
632 ms
ba.js
293 ms
rzd__logo.svg
220 ms
rzd__logo_white.svg
110 ms
icon__eye.svg
115 ms
icon__profile.svg
116 ms
icon__search.svg
109 ms
walk.jpg
666 ms
%D0%9E%D0%BF%D1%80%D0%BE%D1%813.png
422 ms
info__cell_type-director.svg
213 ms
834DA884-C949-4011-B298-2BEC5554F276.jpeg
328 ms
44301D35-051E-4A20-8925-FF7AEDE5A3C0.png
447 ms
C01D6564-20C9-4D95-A6DA-9BC116B65BF8.jpeg
318 ms
rus-novrorod.jpg
328 ms
audioguide.jpg
526 ms
commuter_trains.jpg
545 ms
zoldol.jpg
436 ms
tourist__slide-1.jpg
631 ms
turvagon.jpg
546 ms
meteor-kro.jpg
558 ms
app__hand.png
944 ms
icon__vk_gray.svg
652 ms
icon__izi_gray.jpg
654 ms
footer__logo.jpg
669 ms
icon__swap.svg
709 ms
Gilroy-Bold.woff
730 ms
Gilroy-Black.woff
735 ms
Gilroy-Medium.woff
745 ms
Gilroy-Regular.woff
749 ms
Gilroy-UltraLight.woff
808 ms
icon__prev.svg
833 ms
icon__next.svg
835 ms
info__cell_type_privilege.jpg
1073 ms
icon__up.svg
855 ms
info__cell_type_work.jpg
1011 ms
info__cell_type_scheme.jpg
1158 ms
info__cell_type_economy.jpg
1051 ms
info__cell_type_low-mob.jpg
1077 ms
bx_stat
189 ms
ppk-piter.ru 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
Form elements do not have associated labels
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
ppk-piter.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
ppk-piter.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
![]()
RU
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ppk-piter.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Ppk-piter.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.
ppk-piter.ru
Open Graph description is not detected on the main page of Ppk Piter. 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: