10.5 sec in total
2.5 sec
7 sec
970 ms
Visit puriy.de now to see the best up-to-date Puriy content for Germany and also check out these interesting facts you probably never knew about puriy.de
Der Reiseblog puriy soll Lust machen, die Welt selbst zu entdecken + Tipps zum individuellen und aktiven Reisen + Reiseblog für Südamerika und Afrika Fans
Visit puriy.deWe analyzed Puriy.de page load time and found that the first response time was 2.5 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
puriy.de performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value16.5 s
0/100
25%
Value14.9 s
1/100
10%
Value1,900 ms
8/100
30%
Value0.001
100/100
15%
Value19.0 s
3/100
10%
2546 ms
386 ms
195 ms
874 ms
1067 ms
Our browser made a total of 172 requests to load all elements on the main page. We found that 49% of them (84 requests) were addressed to the original Puriy.de, 19% (33 requests) were made to Scontent.cdninstagram.com and 6% (11 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Puriy.de.
Page size can be reduced by 283.9 kB (11%)
2.7 MB
2.4 MB
In fact, the total size of Puriy.de main page is 2.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. 80% 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 85.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. 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 85.5 kB or 82% of the original size.
Potential reduce by 53.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. Puriy images are well optimized though.
Potential reduce by 92.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 92.6 kB or 49% of the original size.
Potential reduce by 51.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. Puriy.de needs all CSS files to be minified and compressed as it can save up to 51.9 kB or 81% of the original size.
Number of requests can be reduced by 96 (60%)
161
65
The browser has sent 161 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puriy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
puriy.de
2546 ms
wp-emoji-release.min.js
386 ms
amazing-pw.css
195 ms
style.css
874 ms
dashicons.min.css
1067 ms
desktop_style.css
197 ms
styles.css
311 ms
front.css
391 ms
bootstrap.css
695 ms
font-awesome.min.css
466 ms
events_manager.css
479 ms
shariff.min.local.css
489 ms
flexslider.css
561 ms
css
24 ms
genericons.css
575 ms
style.css
586 ms
jetpack.css
752 ms
cp_multicolumn.css
675 ms
wp-cat-list-theme.css
685 ms
wp-cat-list-light.css
771 ms
wp-cat-list-dark.css
783 ms
wp-cat-list-giant-gold-fish.css
786 ms
wp-cat-list-adrift-in-dreams.css
848 ms
jquery.js
1055 ms
jquery-migrate.min.js
880 ms
front_end_script.js
882 ms
bootstrap.min.js
944 ms
front.js
964 ms
chosen.jquery.min.js
979 ms
core.min.js
978 ms
widget.min.js
1040 ms
position.min.js
1063 ms
mouse.min.js
1073 ms
sortable.min.js
1075 ms
datepicker.min.js
1138 ms
menu.min.js
1149 ms
autocomplete.min.js
1158 ms
galleryview.css
978 ms
resizable.min.js
984 ms
platform.js
84 ms
widget.js
283 ms
draggable.min.js
872 ms
devicepx-jetpack.js
4 ms
flexslider.css
878 ms
public.css
871 ms
button.min.js
877 ms
dialog.min.js
804 ms
events-manager.js
796 ms
jquery.fitvids.js
789 ms
jquery.flexslider-min.js
780 ms
functions.js
774 ms
style.css
972 ms
jquery.timers-1.1.2.js
690 ms
jquery.easing.1.3.js
685 ms
jquery.galleryview-2.0.js
673 ms
jquery.form.min.js
681 ms
scripts.js
674 ms
puriy.js
679 ms
comment-reply.min.js
679 ms
wp-embed.min.js
625 ms
jquery.flexslider-min.js
672 ms
jQuery.easing.min.js
660 ms
shariff.js
789 ms
forms-api.min.js
700 ms
pR0sBQVcY0JZc_ciXjFsK5GUMC6XtjipT3aj9UHYjEM.ttf
46 ms
kH7K4InNTm7mmOXXjrA5v-Fc6ciOy_fNLnSqTl1JRpg.ttf
46 ms
cropped-puriy_Logo-150x74.png
1226 ms
cab8c76cd82d94489293b0e7e7edb9bc
146 ms
207c28ae613722953dbf1a82944c21bb
146 ms
49bbeed97751a846d4ae151e95c0a7e6
146 ms
travelbook-white-badge-180.png
727 ms
f5dbc1172a7a5060ec632e2a36a81a13
144 ms
f01bfc3d1245ced9de1cbd0bc71f8f9e
147 ms
Reisenacht_logo-330x300.png
1417 ms
puriy-Slider-Philippinen.jpg
724 ms
puriy_slider-kubas-straende-2.jpg
340 ms
puriy_Slider-pamir-highway.jpg
723 ms
puriy_slider-bogota-graffiti.jpg
725 ms
puriy_Banner_ecuador-cotopaxi1.jpg
724 ms
Tana-6-840x560.jpg
724 ms
Corong-Corong-7-840x560.jpg
722 ms
bohol-philipien-12-840x560.jpg
951 ms
bohol-philipien-24-840x560.jpg
949 ms
Baobabs-Madagascar-840x560.jpg
1106 ms
puriy-reiseblog-galapagos-ecuador-52-840x560.jpg
949 ms
Hotel-Jen-Manila-neu-840x560.jpg
950 ms
Shangri-Las-Mactan-16-840x560.jpg
948 ms
Mad_Kuba_1.jpg
1045 ms
puriy-laender-im-blog-Globus.jpg
1045 ms
puriy_quito-reisefuehrer-1200x800.jpg
1359 ms
uganda_wasser_nandere-1-840x560.jpg
1237 ms
mongolei_gobi_header-840x560.jpg
1050 ms
puriy-reiseblog-mompox-kolumbien-1-840x560.jpg
1331 ms
puriy_quito-reisefuehrer-840x560.jpg
1328 ms
himmel-tauchen-cover-840x560.jpg
1142 ms
rb_kodex.jpg
1206 ms
ga.js
12 ms
__utm.gif
27 ms
2496 ms
Iiwv6KObr74zijHv9BX0bA.ttf
48 ms
rPYmlwqWyhpKafoxVocSUfesZW2xOQ-xsNqO47m55DA.ttf
49 ms
Genericons.svg
1188 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
3 ms
QHIOz1iKF3bIEzRdDFaf5XB5xqB4ifENmctSNDrIeng.ttf
46 ms
cb=gapi.loaded_0
52 ms
cb=gapi.loaded_1
56 ms
page
497 ms
widget55
670 ms
postmessageRelay
401 ms
rs=AGLTcCNSixaVEaRcpL8fP-KmmHNxlc6KVw
13 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
57 ms
rs=AGLTcCNlyN8IeUK1yjlE8qIpJjG5lWWAQw
111 ms
3193398744-postmessagerelay.js
251 ms
rpc:shindig_random.js
101 ms
bg_direction_nav.png
577 ms
photo.jpg
382 ms
mosaik_twitter.jpg
357 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
221 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
221 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
219 ms
rs=AGLTcCNlyN8IeUK1yjlE8qIpJjG5lWWAQw
45 ms
common
154 ms
rs=AGLTcCNlyN8IeUK1yjlE8qIpJjG5lWWAQw
14 ms
cb=gapi.loaded_0
46 ms
combined.css
18 ms
smoothDivScroll.css
4 ms
stack_161235.js
56 ms
jquery.min.js
17 ms
jquery-ui.min.js
43 ms
jquery.mousewheel.min.js
5 ms
jquery.kinetic.js
47 ms
jquery.smoothdivscroll-1.3-min.js
6 ms
analytics.js
66 ms
stackpile.api-6712054ce0.js
83 ms
10838376_916725038446916_312529737_n.jpg
85 ms
big_transparent.gif
45 ms
10362268_872237892902094_811874134_n.jpg
34 ms
1169070_225707357778467_527314760_n.jpg
34 ms
1538408_1117420244959610_1460981270_n.jpg
33 ms
12822323_1708954612679907_1829026223_n.jpg
66 ms
10859996_762703540496755_1197602463_n.jpg
98 ms
11379936_198014347234404_734854739_n.jpg
99 ms
12816983_862049593905380_803860141_n.jpg
53 ms
1171166_1156779717667032_2088387975_n.jpg
36 ms
12822472_1749912201912278_1853606156_n.jpg
262 ms
12783252_161876744202323_438537566_n.jpg
102 ms
10349806_216468682041582_1173857964_n.jpg
123 ms
12797609_261892190808676_866645648_n.jpg
102 ms
12798074_192103884496855_1504676238_n.jpg
165 ms
10731966_1518123538490870_1335610279_n.jpg
116 ms
10570021_1148329828520141_1792926092_n.jpg
140 ms
12751626_1566047727038690_127834097_n.jpg
103 ms
12822476_489430947913277_1906491409_n.jpg
122 ms
12816980_192776767759198_2042421001_n.jpg
117 ms
10326546_600895960058260_700215135_n.jpg
136 ms
12816873_1529628980665766_1183814324_n.jpg
189 ms
12237222_1032853790106859_1575827123_n.jpg
189 ms
12383526_1719088518330118_1951217108_n.jpg
200 ms
12797642_1117624041615175_2015916992_n.jpg
209 ms
12826139_579055858930417_926863562_n.jpg
179 ms
12751399_186508868393617_1281892614_n.jpg
197 ms
12826100_1245489348814500_295209033_n.jpg
205 ms
12797635_218902371798078_633607162_n.jpg
202 ms
12816873_231311183878924_569481741_n.jpg
213 ms
12798168_1655308544732330_1393330654_n.jpg
228 ms
12748318_1679968118929934_1362728221_n.jpg
261 ms
12750201_1560946627566103_1406362368_n.jpg
298 ms
12783407_1682185315368072_362565686_n.jpg
213 ms
collect
12 ms
collect
71 ms
stackpile.api-6712054ce0.js
20 ms
nr-885.min.js
44 ms
puriy.de 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-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
puriy.de 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
Page has valid source maps
puriy.de 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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puriy.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Puriy.de 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.
puriy.de
Open Graph data is detected on the main page of Puriy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: