15.4 sec in total
1.7 sec
10.8 sec
3 sec
Visit prologue.ro now to see the best up-to-date Prologue content for Romania and also check out these interesting facts you probably never knew about prologue.ro
Web design. Realizare site web. Oferim servicii de web design, realizare site web, email marketing, ecommerce, newsletter, cms, seo, webdesign, optimizare site
Visit prologue.roWe analyzed Prologue.ro page load time and found that the first response time was 1.7 sec and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
prologue.ro performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value4.9 s
28/100
25%
Value7.5 s
26/100
10%
Value90 ms
98/100
30%
Value0
100/100
15%
Value4.9 s
78/100
10%
1663 ms
150 ms
309 ms
288 ms
278 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 80% of them (84 requests) were addressed to the original Prologue.ro, 8% (8 requests) were made to Apis.google.com and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Prologue.ro.
Page size can be reduced by 657.8 kB (11%)
5.8 MB
5.1 MB
In fact, the total size of Prologue.ro main page is 5.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. 70% of websites need less resources to load. Images take 5.5 MB which makes up the majority of the site volume.
Potential reduce by 51.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.9 kB or 77% of the original size.
Potential reduce by 450.8 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. Prologue images are well optimized though.
Potential reduce by 117.9 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 117.9 kB or 65% of the original size.
Potential reduce by 37.1 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. Prologue.ro needs all CSS files to be minified and compressed as it can save up to 37.1 kB or 81% of the original size.
Number of requests can be reduced by 31 (30%)
102
71
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prologue. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.prologue.ro
1663 ms
ga.js
150 ms
wp-emoji-release.min.js
309 ms
pagenavi-css.css
288 ms
style.css
278 ms
lightbox.css
271 ms
css
228 ms
lightbox.js
288 ms
script.js
312 ms
cloud-carousel.1.0.5.min.js
505 ms
plusone.js
234 ms
widgets.js
302 ms
wp-embed.min.js
501 ms
__utm.gif
60 ms
jquery.js
374 ms
content_pattern_bg.png
149 ms
header_pattern_bg.png
561 ms
splash_blue.png
3352 ms
splash_purple.png
553 ms
splash_green.png
549 ms
splash_orange.png
544 ms
splash_navy.png
2933 ms
header_city.png
2932 ms
header_birds.png
2921 ms
header_kyte.png
2920 ms
header_childs.png
2929 ms
header_tree.png
3301 ms
header_hills.png
3292 ms
float-contact.png
3293 ms
prologue-logo.png
3289 ms
nav_gradient_bg.png
3293 ms
mid_light_fx.png
3930 ms
lashez.png
3449 ms
greenbee.png
3946 ms
infotour.png
3660 ms
retro.png
4050 ms
retete.png
3714 ms
titiaur.png
3936 ms
logos.png
3938 ms
croaziere1-220x800.png
4798 ms
autosoft1-418x800.png
4801 ms
mcmusic11-252x800.png
4926 ms
strong1-386x800.png
5061 ms
topline1-329x800.png
4926 ms
mobilpay1-238x800.png
4934 ms
directbooking1-194x800.png
5653 ms
homepage-2-franke-419x800.png
5938 ms
homepage-web-design-315x800.png
5934 ms
cupcake1-800x475.jpg
5693 ms
lashez1-497x800.jpg
5701 ms
titiaur1-472x800.jpg
5760 ms
cb=gapi.loaded_0
394 ms
esky1.png
6999 ms
retete1-233x800.jpg
5984 ms
interprepaid1-712x800.png
6617 ms
retro1-629x800.jpg
6377 ms
like.php
2599 ms
infotour1-230x800.jpg
6177 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
226 ms
cb=gapi.loaded_1
212 ms
fastbutton
374 ms
dinengschriftstd-webfont.woff
827 ms
rapid1-423x800.png
4086 ms
mobilpay.jpg
816 ms
mxhost.png
814 ms
xcountry.png
817 ms
postmessageRelay
328 ms
cb=gapi.loaded_0
160 ms
cb=gapi.loaded_1
160 ms
fy8tT2klpgR.js
1056 ms
LVx-xkvaJ0b.png
1096 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
286 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ro.html
185 ms
esky.png
3610 ms
noblesse.jpg
3842 ms
mxhost.jpg
3996 ms
newprologue.jpg
1468 ms
slider_controls.png
850 ms
3193398744-postmessagerelay.js
221 ms
rpc:shindig_random.js
116 ms
splash_services.png
938 ms
mid_bottom.png
707 ms
jot
516 ms
cb=gapi.loaded_0
319 ms
splash_climbing.png
584 ms
splash_bungee.png
582 ms
design_mention.png
698 ms
h_rss.png
702 ms
h_settings.png
821 ms
h_doc.png
635 ms
bbox.png
626 ms
hw_star.png
736 ms
hw_flag.png
745 ms
hw_face.png
856 ms
bbox_splash.png
764 ms
bbox_plane.png
802 ms
splash_services2.png
901 ms
splash_boat.png
790 ms
footer_beach.png
730 ms
footer_boat.png
762 ms
footer_land.png
658 ms
social_sprite.png
795 ms
loading.gif
727 ms
closelabel.gif
770 ms
blank.gif
764 ms
prologue.ro accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
prologue.ro 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
prologue.ro 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
RO
RO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prologue.ro can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Prologue.ro 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.
prologue.ro
Open Graph data is detected on the main page of Prologue. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: