Tools & Wizards About Us

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

wikipoemes.com

Poésie française - Poèmes de poètes de la littérature francophone

Page Load Speed

1.9 sec in total

First Response

114 ms

Resources Loaded

1.6 sec

Page Rendered

231 ms

About Website

Welcome to wikipoemes.com homepage info - get ready to check Wikipoemes best content for Algeria right away, or after learning these important things about wikipoemes.com

Poèmes de poètes de la littérature francophone. Des milliers de poèmes, les grands poètes classiques, romantique et moderne.

Visit wikipoemes.com

Key Findings

We analyzed Wikipoemes.com page load time and found that the first response time was 114 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

wikipoemes.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value5,560 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

wikipoemes.com

114 ms

www.wikipoemes.com

184 ms

style.css

63 ms

style_photo.css

62 ms

wikipoemes.jpg

95 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 61% of them (73 requests) were addressed to the original Wikipoemes.com, 5% (6 requests) were made to C.betrad.com and 5% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (475 ms) relates to the external source Delivery.myswitchads.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 184.2 kB (36%)

Content Size

513.8 kB

After Optimization

329.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wikipoemes.com main page is 513.8 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. 40% of websites need less resources to load. Javascripts take 285.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 41.7 kB

  • Original 49.5 kB
  • After minification 44.5 kB
  • After compression 7.8 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 41.7 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 4.7 kB

  • Original 164.4 kB
  • After minification 159.6 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. Wikipoemes images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 126.2 kB

  • Original 285.9 kB
  • After minification 285.6 kB
  • After compression 159.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 126.2 kB or 44% of the original size.

CSS Optimization

-83%

Potential reduce by 11.6 kB

  • Original 14.0 kB
  • After minification 10.6 kB
  • After compression 2.4 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. Wikipoemes.com needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (25%)

Requests Now

114

After Optimization

86

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

wikipoemes.com accessibility score

76

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

wikipoemes.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

wikipoemes.com SEO score

76

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    N/A

  • 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 Wikipoemes.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wikipoemes.com 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

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