Tools & Wizards About Us
keep.pt screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

keep.pt

KEEP SOLUTIONS - Soluções avançadas para gestão e preservação de informação

Page Load Speed

5 sec in total

First Response

1.3 sec

Resources Loaded

3.4 sec

Page Rendered

235 ms

keep.pt screenshot

About Website

Welcome to keep.pt homepage info - get ready to check KEEP best content for Portugal right away, or after learning these important things about keep.pt

Soluções avançadas para gestão e preservação de informação especialmente desenhadas para Arquivos, Bibliotecas e Museus.

Visit keep.pt

Key Findings

We analyzed Keep.pt page load time and found that the first response time was 1.3 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

keep.pt performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.615

10/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

www.keep.pt

1326 ms

style.css

10 ms

default_skin.css

10 ms

skin_builder.php

255 ms

shortcodes.css

13 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 78% of them (56 requests) were addressed to the original Keep.pt, 8% (6 requests) were made to Static.hupso.com and 7% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Keep.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 214.0 kB (25%)

Content Size

857.1 kB

After Optimization

643.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Keep.pt main page is 857.1 kB. 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 603.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 27.7 kB

  • Original 35.1 kB
  • After minification 33.4 kB
  • After compression 7.4 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 27.7 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 27.7 kB

  • Original 603.9 kB
  • After minification 576.3 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. KEEP images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 80.9 kB

  • Original 123.6 kB
  • After minification 94.6 kB
  • After compression 42.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 80.9 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 77.8 kB

  • Original 94.6 kB
  • After minification 71.9 kB
  • After compression 16.8 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. Keep.pt needs all CSS files to be minified and compressed as it can save up to 77.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (61%)

Requests Now

66

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.keep.pt

www.keep.pt

1326 ms

style.css

style.css

10 ms

default_skin.css

default_skin.css

10 ms

skin_builder.php

skin_builder.php

255 ms

shortcodes.css

shortcodes.css

13 ms

css

css

26 ms

css

css

44 ms

nivo-slider.css

nivo-slider.css

13 ms

fix.css

fix.css

14 ms

catalog.css

catalog.css

14 ms

ecart.css

ecart.css

18 ms

colorbox.css

colorbox.css

14 ms

style.css

style.css

14 ms

pagenavi-css.css

pagenavi-css.css

16 ms

wps-seo-booster-front.css

wps-seo-booster-front.css

15 ms

jquery.min.js

jquery.min.js

14 ms

superfish.js

superfish.js

16 ms

hoverIntent.js

hoverIntent.js

16 ms

jquery.bgiframe.min.js

jquery.bgiframe.min.js

16 ms

supersubs.js

supersubs.js

17 ms

easing.js

easing.js

18 ms

flowplayer-3.2.4.min.js

flowplayer-3.2.4.min.js

18 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

20 ms

jquery.tools.tabs.min.js

jquery.tools.tabs.min.js

17 ms

block.js

block.js

20 ms

custom.js

custom.js

19 ms

share_toolbar.js

share_toolbar.js

199 ms

scripts.php

scripts.php

47 ms

typography.php

typography.php

203 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

66 ms

ga.js

ga.js

47 ms

dot.png

dot.png

140 ms

body.gif

body.gif

41 ms

logo_keep_home3.png

logo_keep_home3.png

38 ms

menu_cloud_blue.png

menu_cloud_blue.png

39 ms

slider_bottom.png

slider_bottom.png

39 ms

ajax-loader.gif

ajax-loader.gif

39 ms

banner_21.jpg

banner_21.jpg

41 ms

banner_physicalarchival.jpg

banner_physicalarchival.jpg

44 ms

banner_educationalpartnerships.jpg

banner_educationalpartnerships.jpg

40 ms

banner_libraries.jpg

banner_libraries.jpg

42 ms

banner_museums.jpg

banner_museums.jpg

42 ms

banner_municipality2.jpg

banner_municipality2.jpg

47 ms

feat_line.png

feat_line.png

40 ms

archeevo4-frontpage.png

archeevo4-frontpage.png

47 ms

museo_highlight.png

museo_highlight.png

44 ms

1358094802_07_rss.png

1358094802_07_rss.png

43 ms

logo_nano_archeevo.png

logo_nano_archeevo.png

43 ms

logo_nano_koha_2.png

logo_nano_koha_2.png

44 ms

logo_nano_retrievo_2.png

logo_nano_retrievo_2.png

46 ms

logo_nano_dspace_2.png

logo_nano_dspace_2.png

44 ms

logo_nano_weebox_2.png

logo_nano_weebox_2.png

47 ms

logo_nano_roda_2.png

logo_nano_roda_2.png

46 ms

logo_nano_moodle.png

logo_nano_moodle.png

48 ms

pt.png

pt.png

49 ms

en.png

en.png

46 ms

twitter.png

twitter.png

155 ms

facebook.png

facebook.png

186 ms

googleplus.png

googleplus.png

187 ms

linkedin.png

linkedin.png

190 ms

s-BiyweUPV0v-yRb-cjciMDdSZkkecOE1hvV7ZHvhyU.ttf

s-BiyweUPV0v-yRb-cjciMDdSZkkecOE1hvV7ZHvhyU.ttf

82 ms

EFpQQyG9GqCrobXxL-KRMcBaWKZ57bY3RXgXH6dOjZ0.ttf

EFpQQyG9GqCrobXxL-KRMcBaWKZ57bY3RXgXH6dOjZ0.ttf

83 ms

QQt14e8dY39u-eYBZmppwTdGNerWpg2Hn6A-BxWgZ_I.ttf

QQt14e8dY39u-eYBZmppwTdGNerWpg2Hn6A-BxWgZ_I.ttf

83 ms

cj2hUnSRBhwmSPr9kS5892cbqnd1g9zt-QKibAzZSRA.ttf

cj2hUnSRBhwmSPr9kS5892cbqnd1g9zt-QKibAzZSRA.ttf

82 ms

c92rD_x0V1LslSFt3-QEpsff8iMd5lHP9j3QUuXTy8g.ttf

c92rD_x0V1LslSFt3-QEpsff8iMd5lHP9j3QUuXTy8g.ttf

83 ms

loading.gif

loading.gif

50 ms

__utm.gif

__utm.gif

16 ms

controls.png

controls.png

12 ms

arr-prev.png

arr-prev.png

5 ms

arr-next.png

arr-next.png

3 ms

page_nav_active_black.png

page_nav_active_black.png

4 ms

page_nav.png

page_nav.png

5 ms

Accessibility Review

keep.pt accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

keep.pt best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

keep.pt SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keep.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Keep.pt 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.

Social Sharing Optimization

keep.pt

Open Graph data is detected on the main page of KEEP. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: