Tools & Wizards About Us
wordscore.pt screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wordscore.pt

WordScore - Soluções Tecnológicas

Page Load Speed

2.5 sec in total

First Response

241 ms

Resources Loaded

1.9 sec

Page Rendered

313 ms

wordscore.pt screenshot

About Website

Visit wordscore.pt now to see the best up-to-date Word Score content and also check out these interesting facts you probably never knew about wordscore.pt

WordScore Soluções Tecnológicas

Visit wordscore.pt

Key Findings

We analyzed Wordscore.pt page load time and found that the first response time was 241 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wordscore.pt performance score

0

Network Requests Diagram

wordscore.pt

241 ms

www.wordscore.pt

318 ms

style.css

215 ms

skitter.styles.css

194 ms

style.css

287 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 88% of them (57 requests) were addressed to the original Wordscore.pt, 8% (5 requests) were made to Cdn.ywxi.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (775 ms) belongs to the original domain Wordscore.pt.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

832.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wordscore.pt main page is 1.1 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. 25% of websites need less resources to load. Images take 767.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 17.2 kB

  • Original 22.5 kB
  • After minification 19.8 kB
  • After compression 5.3 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 2.7 kB, which is 12% 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 17.2 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 23.4 kB

  • Original 767.5 kB
  • After minification 744.1 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. Word Score images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 202.1 kB

  • Original 277.9 kB
  • After minification 242.5 kB
  • After compression 75.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 202.1 kB or 73% of the original size.

CSS Optimization

-82%

Potential reduce by 34.9 kB

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

Requests Breakdown

Number of requests can be reduced by 29 (48%)

Requests Now

61

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wordscore.pt

wordscore.pt

241 ms

www.wordscore.pt

www.wordscore.pt

318 ms

style.css

style.css

215 ms

skitter.styles.css

skitter.styles.css

194 ms

style.css

style.css

287 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

502 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

210 ms

jquery.animate-colors-min.js

jquery.animate-colors-min.js

210 ms

jquery.skitter.js

jquery.skitter.js

437 ms

hoverIntent.js

hoverIntent.js

296 ms

superfish.js

superfish.js

301 ms

supersubs.js

supersubs.js

300 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

369 ms

VideoPlayerV1.js

VideoPlayerV1.js

459 ms

Background%201.jpg

Background%201.jpg

403 ms

logo.png

logo.png

94 ms

wslide1.jpg

wslide1.jpg

312 ms

wslide2.jpg

wslide2.jpg

261 ms

wslide3.jpg

wslide3.jpg

278 ms

wslide4.jpg

wslide4.jpg

363 ms

wslide5.jpg

wslide5.jpg

257 ms

wslide6.jpg

wslide6.jpg

425 ms

shadow-img-slider.png

shadow-img-slider.png

343 ms

pattern_box.gif

pattern_box.gif

356 ms

glow.png

glow.png

389 ms

icon10.png

icon10.png

436 ms

icon11.png

icon11.png

448 ms

icon12.png

icon12.png

448 ms

pattern_title.gif

pattern_title.gif

467 ms

wpic1.jpg

wpic1.jpg

489 ms

shadowimg220.gif

shadowimg220.gif

507 ms

wpic2.jpg

wpic2.jpg

518 ms

wpic3.jpg

wpic3.jpg

537 ms

wpic4.jpg

wpic4.jpg

624 ms

bg-footer.png

bg-footer.png

544 ms

bg-footer-pattern.gif

bg-footer-pattern.gif

567 ms

noticiaSmall1.jpg

noticiaSmall1.jpg

595 ms

opacity-img.png

opacity-img.png

596 ms

noticiaSmall2.jpg

noticiaSmall2.jpg

614 ms

produtoSmall1.jpg

produtoSmall1.jpg

636 ms

produtoSmall2.jpg

produtoSmall2.jpg

647 ms

produtoSmall3.jpg

produtoSmall3.jpg

686 ms

produtoSmall4.jpg

produtoSmall4.jpg

688 ms

produtoSmall5.jpg

produtoSmall5.jpg

692 ms

produtoSmall6.jpg

produtoSmall6.jpg

712 ms

bg-afterfooter.png

bg-afterfooter.png

728 ms

fb.png

fb.png

724 ms

stumbleupon.png

stumbleupon.png

775 ms

lastfm.png

lastfm.png

764 ms

twitter.png

twitter.png

769 ms

analytics.js

analytics.js

27 ms

1.js

1.js

27 ms

101.gif

101.gif

182 ms

collect

collect

13 ms

host.js

host.js

188 ms

Ubuntu-R-webfont.woff

Ubuntu-R-webfont.woff

716 ms

tm-float-bg-right-bottom.png

tm-float-bg-right-bottom.png

4 ms

ajax

ajax

326 ms

float2-right.png

float2-right.png

185 ms

youtube.png

youtube.png

556 ms

prev.png

prev.png

552 ms

next.png

next.png

568 ms

opacity-slider-text.png

opacity-slider-text.png

540 ms

ajax-loader.gif

ajax-loader.gif

523 ms

Ubuntu-R-webfont.ttf

Ubuntu-R-webfont.ttf

91 ms

SEO Factors

wordscore.pt SEO score

0

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 Wordscore.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 Wordscore.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

wordscore.pt

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