Tools & Wizards About Us
pke.net screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

pke.net

Reisen Travel Kessler Trogen Appenzeller Alpen Ghostwriting New Zealand Neuseeland Cook Islands Southpacific online-office Medien Ostschweiz Bodensee ...

Page Load Speed

3.6 sec in total

First Response

563 ms

Resources Loaded

2.8 sec

Page Rendered

295 ms

pke.net screenshot

About Website

Welcome to pke.net homepage info - get ready to check Pke best content right away, or after learning these important things about pke.net

Online-office K - Reisen, Travel, Inseln, Familien, Appenzellerland, South Pacific Gewerbe and Ghostwriting

Visit pke.net

Key Findings

We analyzed Pke.net page load time and found that the first response time was 563 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

pke.net performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

pke.net

563 ms

ga.js

6 ms

hgrund.gif

226 ms

fed6.gif

418 ms

__utm.gif

12 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 19% of them (14 requests) were addressed to the original Pke.net, 38% (28 requests) were made to Heizplan.solarlog-web.ch and 27% (20 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (735 ms) belongs to the original domain Pke.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 536.0 kB (34%)

Content Size

1.6 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pke.net main page is 1.6 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. 55% of websites need less resources to load. Images take 837.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 14.7 kB

  • Original 19.6 kB
  • After minification 17.6 kB
  • After compression 4.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 14.7 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 13.5 kB

  • Original 837.2 kB
  • After minification 823.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. Pke images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 432.6 kB

  • Original 636.5 kB
  • After minification 633.9 kB
  • After compression 203.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 432.6 kB or 68% of the original size.

CSS Optimization

-89%

Potential reduce by 75.2 kB

  • Original 84.7 kB
  • After minification 57.0 kB
  • After compression 9.5 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. Pke.net needs all CSS files to be minified and compressed as it can save up to 75.2 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (26%)

Requests Now

69

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pke.net

pke.net

563 ms

ga.js

ga.js

6 ms

hgrund.gif

hgrund.gif

226 ms

fed6.gif

fed6.gif

418 ms

__utm.gif

__utm.gif

12 ms

sw-home.gif

sw-home.gif

215 ms

email.gif

email.gif

212 ms

office.gif

office.gif

213 ms

nz.gif

nz.gif

311 ms

cooks.gif

cooks.gif

325 ms

gallery.gif

gallery.gif

446 ms

cyprus.gif

cyprus.gif

444 ms

usa.gif

usa.gif

453 ms

trogen.gif

trogen.gif

523 ms

links.gif

links.gif

560 ms

family.jpg

family.jpg

735 ms

widgets.js

widgets.js

83 ms

dashboard

dashboard

318 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

127 ms

syndication

syndication

97 ms

291563678438932480

291563678438932480

157 ms

130 ms

proxy.jpg

proxy.jpg

79 ms

proxy.jpg

proxy.jpg

44 ms

proxy.jpg

proxy.jpg

43 ms

proxy.jpg

proxy.jpg

82 ms

proxy.jpg

proxy.jpg

82 ms

proxy.jpg

proxy.jpg

121 ms

proxy.jpg

proxy.jpg

115 ms

proxy.jpg

proxy.jpg

119 ms

proxy.jpg

proxy.jpg

121 ms

proxy.jpg

proxy.jpg

93 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

32 ms

reset.css

reset.css

117 ms

main.css

main.css

217 ms

all-lib-1.2.2.min.js

all-lib-1.2.2.min.js

632 ms

all-dashboard-1.4.7.min.js

all-dashboard-1.4.7.min.js

317 ms

main.js

main.js

212 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

55 ms

11034fdf7da6dd3114c56c7f1f1d6096_normal.png

11034fdf7da6dd3114c56c7f1f1d6096_normal.png

171 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

39 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

67 ms

proxy.jpg

proxy.jpg

38 ms

proxy.jpg

proxy.jpg

7 ms

proxy.jpg

proxy.jpg

7 ms

proxy.jpg

proxy.jpg

38 ms

proxy.jpg

proxy.jpg

68 ms

proxy.jpg

proxy.jpg

33 ms

proxy.jpg

proxy.jpg

66 ms

proxy.jpg

proxy.jpg

54 ms

proxy.jpg

proxy.jpg

28 ms

proxy.jpg

proxy.jpg

4 ms

cust_js.js

cust_js.js

321 ms

cust_css.js

cust_css.js

119 ms

api

api

141 ms

loader.gif

loader.gif

206 ms

background.png

background.png

517 ms

head_background.png

head_background.png

106 ms

logo.png

logo.png

106 ms

head_icons.png

head_icons.png

208 ms

head_bottom.png

head_bottom.png

209 ms

border-bottom.png

border-bottom.png

210 ms

border-right.png

border-right.png

234 ms

bar_bg_left.png

bar_bg_left.png

311 ms

bar_bg.png

bar_bg.png

311 ms

bar_bg_prev.png

bar_bg_prev.png

312 ms

bar_bg_next.png

bar_bg_next.png

313 ms

separator_weather_bg.png

separator_weather_bg.png

337 ms

boxshadow.png

boxshadow.png

414 ms

bar_bg_right.png

bar_bg_right.png

415 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

612 ms

OpenSans-Light-webfont.woff

OpenSans-Light-webfont.woff

616 ms

jot.html

jot.html

27 ms

api

api

348 ms

Accessibility Review

pke.net accessibility score

71

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

<object> elements do not have alternate text

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

pke.net best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pke.net SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document uses plugins

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pke.net 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 Pke.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

pke.net

Open Graph description is not detected on the main page of Pke. 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: