Report Summary

  • 19

    Performance

    Renders faster than
    39% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    34% of websites

  • 84

    SEO

    Google-friendlier than
    60% of websites

noa.al

NOA Lajme - Agjencia Kombëtare e Lajmeve

Page Load Speed

9.6 sec in total

First Response

36 ms

Resources Loaded

3.6 sec

Page Rendered

5.9 sec

noa.al screenshot

About Website

Welcome to noa.al homepage info - get ready to check NOA best content for Albania right away, or after learning these important things about noa.al

NOA - Agjencia Kombëtare e Lajmeve - E vetmja 24 orë, minutë pas minute, lajme nga Shqipëria, Kosova, Maqedonia dhe pjesa tjetër e botës

Visit noa.al

Key Findings

We analyzed Noa.al page load time and found that the first response time was 36 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

noa.al performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value3,200 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.104

88/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

noa.al

36 ms

www.noa.al

88 ms

uikit.min.css

19 ms

newstyle.css

27 ms

base_new.css

26 ms

Our browser made a total of 243 requests to load all elements on the main page. We found that 73% of them (177 requests) were addressed to the original Noa.al, 7% (16 requests) were made to B.am-st.net and 3% (8 requests) were made to Code.createjs.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source .

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (30%)

Content Size

3.7 MB

After Optimization

2.6 MB

In fact, the total size of Noa.al main page is 3.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. 85% 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.

HTML Optimization

-85%

Potential reduce by 203.7 kB

  • Original 240.0 kB
  • After minification 227.7 kB
  • After compression 36.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. 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 203.7 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 114.4 kB

  • Original 2.3 MB
  • After minification 2.2 MB

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. NOA images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 659.3 kB

  • Original 940.7 kB
  • After minification 940.7 kB
  • After compression 281.5 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 659.3 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 136.6 kB

  • Original 166.9 kB
  • After minification 146.5 kB
  • After compression 30.3 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. Noa.al needs all CSS files to be minified and compressed as it can save up to 136.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (27%)

Requests Now

236

After Optimization

173

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

Accessibility Review

noa.al accessibility score

71

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 input fields do not have accessible names

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

noa.al best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

noa.al SEO score

84

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

Content Best Practices

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SQ

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Noa.al can be misinterpreted by Google and other search engines. Our service has detected that Albanian 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 Noa.al 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

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